Date: Thu, 20 Jun 2002 15:43:40 -0400 From: "Gary Thorpe" <gat7634@hotmail.com> To: freebsd-arch@freebsd.org Subject: Re: multiple threads for interrupts Message-ID: <F112l4rhYQYx3G5aYY6000252ae@hotmail.com>
next in thread | raw e-mail | index | archive | help
>From: Terry Lambert <tlambert2@mindspring.com> >To: Seigo Tanimura <tanimura@r.dl.itc.u-tokyo.ac.jp> >CC: arch@FreeBSD.org >Subject: Re: multiple threads for interrupts >Date: Thu, 20 Jun 2002 04:18:24 -0700 > >Seigo Tanimura wrote: > > One solution is to run multiple threads for each of the interrupt > > types. Since I noticed this issue first during my work of network > > locking, I have been tweaking the swi subsystem so that it runs > > multiple threads for an swi type. For those who are interested, the > > patch can be found at: > > > > http://people.FreeBSD.org/~tanimura/patches/swipool.diff.gz > >Benchmarks before and after, demonstrating an improvement? > >-- Terry I am not a kernel programmer, but I have read a paper which concludes that making threads have an "affinity" or "stickiness" to the last CPU it was run on is benifical because it leads to less cache flushing/refilling. Maybe this will be a factor in having multiple threads for interrupt handling? _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F112l4rhYQYx3G5aYY6000252ae>