on 06/03/2008 14:55 John Baldwin said the following:
On Monday 18 February 2008 10:25:13 am Andriy Gapon wrote:
I see that sched_4bsd has a NOP callout with a purpose of forcing a
context switch (via softclock), so that something like a preemption
could happen (e.g. for threads in a tight
On Monday 18 February 2008 10:25:13 am Andriy Gapon wrote:
I see that sched_4bsd has a NOP callout with a purpose of forcing a
context switch (via softclock), so that something like a preemption
could happen (e.g. for threads in a tight calculation loop).
What serves the similar purpose for
On Thursday 06 March 2008 08:40:10 am Andriy Gapon wrote:
on 06/03/2008 14:55 John Baldwin said the following:
On Monday 18 February 2008 10:25:13 am Andriy Gapon wrote:
I see that sched_4bsd has a NOP callout with a purpose of forcing a
context switch (via softclock), so that something
I see that sched_4bsd has a NOP callout with a purpose of forcing a
context switch (via softclock), so that something like a preemption
could happen (e.g. for threads in a tight calculation loop).
What serves the similar purpose for sched_ule?
Or, how sched_ule deals with the issue without
4 matches
Mail list logo
