Date: Fri, 28 Jan 2011 11:32:19 +0100 From: Damien Fleuriot <ml@my.gd> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: Sergey Lobanov <wmn@siberianet.ru>, "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, "freebsd-pf@freebsd.org" <freebsd-pf@freebsd.org> Subject: Re: High interrupt rate on a PF box + performance Message-ID: <4D429B33.2010402@my.gd> In-Reply-To: <20110127205845.GA41537@icarus.home.lan> References: <4D41417A.20904@my.gd> <1DB50624F8348F48840F2E2CF6040A9D014BEB8833@orsmsx508.amr.corp.intel.com> <4D41B197.6070308@my.gd> <201101280146.57028.wmn@siberianet.ru> <4D41C9FC.10503@my.gd> <20110127195741.GA40449@icarus.home.lan> <4D41D7BE.3030208@my.gd> <20110127205845.GA41537@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/27/11 9:58 PM, Jeremy Chadwick wrote: > > Kernel folks should be able to talk about this in detail, but my > understanding is that the kernel itself supports multiple threads, but > the question is whether or not the drivers or relevant "pieces" (e.g. > igb(4) driver, pf, TCP stack, etc.) support SMP (multi-core/threading) > or not. I think this is referred to as something being "MPSAFE" or not. > > The things you see during boot -- [ITHREAD], [FILTER], and > [GIANT-LOCKED] play a role as well, but I think those indicate what > style of locking is used (since some drivers/features might not work > properly in a multiprocessor environment). > > I'm trying to avoid correlating "multiprocessor safe" with "makes use of > multiple processors". I'm an old 65xxx CPU guy, this SMP stuff is still > "new technology" to me when it comes to actual operations/mechanics. > > Regarding TCP and SMP, this is regularly touched on in the FreeBSD > Status Reports that go out (always worth reading). See "TCP SMP > scalability project": > > http://www.freebsd.org/news/status/report-2010-10-2010-12.html > > I know all this information is technical of course and doesn't answer > your question directly. I wish there was something more authoritative > when it came to this question. > Thanks for your time explaining all this, I'll have a look at your link, even if it may or may not apply directly to our case, it'll still be interesting material. I'll have to poke around for information about the kernel and how it works with multithreading :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D429B33.2010402>