|To:||Andrew Morton <andrewm@xxxxxxxxxx>|
|Subject:||Re: modular net drivers|
|From:||Philipp Rumpf <prumpf@xxxxxxxx>|
|Date:||Sat, 24 Jun 2000 19:45:06 -0700|
|Cc:||Richard Gooch <rgooch@xxxxxxxxxxxxxxx>, Rusty Russell <rusty@xxxxxxxxxxxxxxxx>, Keith Owens <kaos@xxxxxxxxxx>, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx>|
|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> <20000624093548.A31621@puffin.external.hp.com> <200006241548.e5OFmiC09138@vindaloo.ras.ucalgary.ca> <39556E6E.DE0DAA90@uow.edu.au>|
On Sun, Jun 25, 2000 at 12:29:02PM +1000, Andrew Morton wrote: > My patch was quite bogus, of course :( We can have as many threads as > we like spinning and the scheduler will cheerfully timeslice between > them. 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.
|<Prev in Thread]||Current Thread||[Next in Thread>|