Farid Hajji
2012-04-23 15:09:28 UTC
Hello,
I'm experimenting with user space scheduling on L4Ka::Pistachio
(amd64) as specified in the paper
"Towards Effective User-Controlled Scheduling for Microkernel-Based Systems"
and I'd like a worker thread to RPC its associated scheduler
thread, when it has used up its total quantum.
This however never seems to happen. In the KDB, I always see
that 'tq' is set to 0usec, in other words, to L4_Never. Is it right
that the user space scheduler would never be RPC-ed in this case?
So I've tried to change the 'tq' with a call to L4_Set_Timeslice().
But even then, the 'tq' always remain at 0usec, and what's worse,
the time slice also jumps to 0usec, even when set to some other
value.
Is the call to L4_Set_Timeslice() broken?
Attached is a simple test case, and the output of KDB before
and after the call to L4_Set_Timeslice().
Thanks in advance,
-Farid Hajji.
I'm experimenting with user space scheduling on L4Ka::Pistachio
(amd64) as specified in the paper
"Towards Effective User-Controlled Scheduling for Microkernel-Based Systems"
and I'd like a worker thread to RPC its associated scheduler
thread, when it has used up its total quantum.
This however never seems to happen. In the KDB, I always see
that 'tq' is set to 0usec, in other words, to L4_Never. Is it right
that the user space scheduler would never be RPC-ed in this case?
So I've tried to change the 'tq' with a call to L4_Set_Timeslice().
But even then, the 'tq' always remain at 0usec, and what's worse,
the time slice also jumps to 0usec, even when set to some other
value.
Is the call to L4_Set_Timeslice() broken?
Attached is a simple test case, and the output of KDB before
and after the call to L4_Set_Timeslice().
Thanks in advance,
-Farid Hajji.