netdev
[Top] [All Lists]

Re: modular net drivers

To: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Subject: Re: modular net drivers
From: Philipp Rumpf <prumpf@xxxxxxxx>
Date: Sat, 24 Jun 2000 19:54:39 -0700
Cc: Andrew Morton <andrewm@xxxxxxxxxx>, Rusty Russell <rusty@xxxxxxxxxxxxxxxx>, Keith Owens <kaos@xxxxxxxxxx>, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx>
In-reply-to: <200006250247.e5P2lX217879@vindaloo.ras.ucalgary.ca>
References: <20000624093548.A31621@puffin.external.hp.com> <20000623164805.AA5BB8154@halfway> <3954262D.60BDEF41@uow.edu.au> <20000624080106.A25102@fruits.uzix.org> <3954D42A.938A724B@uow.edu.au> <200006241548.e5OFmiC09138@vindaloo.ras.ucalgary.ca> <39556E6E.DE0DAA90@uow.edu.au> <20000624194506.B25473@fruits.uzix.org> <200006250247.e5P2lX217879@vindaloo.ras.ucalgary.ca>
Sender: owner-netdev@xxxxxxxxxxx
On Sat, Jun 24, 2000 at 08:47:33PM -0600, Richard Gooch wrote:
> Philipp Rumpf writes:
> > Oh ?  I wasn't aware kernel_threads could be rescheduled, unlike
> > normal kernel code, and in fact I still don't see how they would.
> 
> They can't. Once you're running in the kernel, you can't be pre-empted
> by another thread, unless you sleep or otherwise call schedule().

Nod, that's what it looked like to me.  Andrew, take your thinking cap
off again.

<Prev in Thread] Current Thread [Next in Thread>