[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080730133527.GI10471@solarflare.com>
Date: Wed, 30 Jul 2008 14:35:29 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: David Miller <davem@...emloft.net>
Cc: tony.luck@...el.com, jgarzik@...hat.com,
linux-kernel@...r.kernel.org, linux-ia64@...r.kernel.org,
netdev@...r.kernel.org, matthew@....cx, holt@....com,
linux-net-drivers@...arflare.com
Subject: Re: [Patch] fix ia64 build failure when CONFIG_SFC=m
David Miller wrote:
> From: Ben Hutchings <bhutchings@...arflare.com>
> Date: Tue, 29 Jul 2008 18:48:41 +0100
>
> > I think a single core in each package can generally saturate the
> > memory bus and this is why spreading the load wider is not useful.
>
> I disagree, especially for routing and firewall setups.
>
> You want as many cpu threads as possible, even on the same core,
> doing the routing and firewall lookups through the various
> datastructures, in parallel.
So far as I can see, hardly anyone is doing routing at 10G speeds on Linux.
If they were, the horrible interaction with LRO would presumably have been
found and fixed earlier. Besides which, internal benchmarking showed that we
could route 1500-byte packets bidirectionally at very near line rate using one
core on each of two multi-core packages. (I can give more details if you
want.) The default can in any case be overridden using the rss_cpus module
parameter. If you want to add a core network setting for that, I think we'd
be happy to use it.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists