On 28-Nov-01 Bruce Evans wrote:
> On Mon, 26 Nov 2001, John Baldwin wrote:
>
>> We don't do preemption in the kernel yet, so they need to yield the CPU when
>> another thread is available. The page zeroing thread does this wrong as it
>> should check procrunnable() instead of switching after do
On Mon, 26 Nov 2001, John Baldwin wrote:
> We don't do preemption in the kernel yet, so they need to yield the CPU when
> another thread is available. The page zeroing thread does this wrong as it
> should check procrunnable() instead of switching after doing N pages. The idle
Except it would
On 23-Nov-01 Luigi Rizzo wrote:
> In order to port my network polling stuff to current, I was looking
> at ways to do things within the "idle loop", and was pointed to
> the idle_proc() or vm_pagezero() . I am listing below the code
> for these kernel threads (I hope the name is the correct one)
Luigi Rizzo wrote:
> Now, the whole problem here seems to be that kernel threads
> are not preemptable, which is something that worries me a
> bit because in CURRENT we use them for interrupt handlers as
> well, and those used to be preemptable (subject to spl masks)
> in RELENG_4.
No, the kernel
Now, the whole problem here seems to be that kernel threads
are not preemptable, which is something that worries me a
bit because in CURRENT we use them for interrupt handlers as
well, and those used to be preemptable (subject to spl masks)
in RELENG_4.
On the other hand, if preemptable threads a
On Fri, 23 Nov 2001, Peter Wemm wrote:
> Luigi Rizzo wrote:
> > My understanding is that idle_loop threads _need_ to give up the cpu
> > because they are special: they must never be in a run queue, and the
> > scheduler knows about them (as a matter of fact, I cannot see where
> > in kern/kern_id
On 25-Oct-01 Luigi Rizzo wrote:
> I have some code (in stable) which is invoked from the idle
> loop, see below. I was trying to port it to CURRENT, but
> cannot find where the idle_loop (or idlethread ?) has gone.
> Any pointers ? A grep for idlethread did not return
> anything that i could pars
I have some code (in stable) which is invoked from the idle
loop, see below. I was trying to port it to CURRENT, but
cannot find where the idle_loop (or idlethread ?) has gone.
Any pointers ? A grep for idlethread did not return
anything that i could parse.
Furthermore, what kind of locking shoul
