Re: PATCH: 8139too kernel thread

2000-11-16 Thread Jeff Garzik
Linus Torvalds wrote: > But yes, on 2.4.x the cost of threads is fairly low. The biggest cost by > far is probably the locking needed for the scheduler etc, and there the > best rule of thumb is probably to see whether the driver really ends up > being noticeably simpler. My main motivations for

Re: PATCH: 8139too kernel thread

2000-11-16 Thread Alan Cox
> > 8K of memory, two tlb flushes, cache misses on the scheduler. The price is > ^^^ > > actually extremely high. > > > Does it really need non-lazy TLB? Good point, so its a mere 8K of memory and the scheduler cache misses > I'm not saying that it's a good idea, bu

Re: PATCH: 8139too kernel thread

2000-11-16 Thread Linus Torvalds
On Thu, 16 Nov 2000, Alexander Viro wrote: > > On Thu, 16 Nov 2000, Alan Cox wrote: > > > > The only disadvantage to this scheme is the added cost of a kernel > > > thread over a kernel timer. I think this is an ok cost, because this > > > is a low-impact thread that sleeps a lot.. > > > > 8

Re: PATCH: 8139too kernel thread

2000-11-16 Thread Alexander Viro
On Thu, 16 Nov 2000, Alan Cox wrote: > > The only disadvantage to this scheme is the added cost of a kernel > > thread over a kernel timer. I think this is an ok cost, because this > > is a low-impact thread that sleeps a lot.. > > 8K of memory, two tlb flushes, cache misses on the scheduler.

Re: PATCH: 8139too kernel thread

2000-11-16 Thread Alan Cox
> The only disadvantage to this scheme is the added cost of a kernel > thread over a kernel timer. I think this is an ok cost, because this > is a low-impact thread that sleeps a lot.. 8K of memory, two tlb flushes, cache misses on the scheduler. The price is actually extremely high. - To unsub

Re: PATCH: 8139too kernel thread

2000-11-10 Thread Andrew Morton
Jeff Garzik wrote: > > (note Linus, not for applying...) > > Here is a patch, against 2.4.0-test11-pre2, that I wanted to forward > to the lists for comment. > > Many of the ethernet drivers have timer routines, which are > called every three-five seconds or so. These timer routines > typicall

PATCH: 8139too kernel thread

2000-11-10 Thread Jeff Garzik
(note Linus, not for applying...) Here is a patch, against 2.4.0-test11-pre2, that I wanted to forward to the lists for comment. Many of the ethernet drivers have timer routines, which are called every three-five seconds or so. These timer routines typically do stuff related to media selection