From: Ben Hutchings <bhutchings@solarflare.com>
To: Tom Herbert <therbert@google.com>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
Max Krasnyanskiy <maxk@qualcomm.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: RFC [PATCH net-2.6 1/6] net: Scheduling softirqs between CPUSs
Date: Wed, 12 Mar 2008 15:10:52 +0000 [thread overview]
Message-ID: <20080312151051.GI26963@solarflare.com> (raw)
In-Reply-To: <65634d660803111648l15c4d653t52b4fc9e8dfa531d@mail.gmail.com>
Tom Herbert wrote:
> > Recent versions of Windows that are aware of RSS will instruct network
> > drivers to update their RSS indirection tables so that received
> > packets are handled on the same CPU as the thread likely to use the
> > received data. This requires that the network stack knows the hash
> > function, so Microsoft specified a "Toeplitz hash" for IPv4 and IPv6.
> > You can expect that most hardware RSS implementations will use this
> > function and not a simple XOR.
> >
>
> Thanks. I am planning to do the Toeplitz hash in the softRSS. Also,
> I was planning to add support for devices that provide the Toeplitz
> hash but don't do full RSS.
>
> One nice feature about Microsoft RSS seems to be the ability for the
> stack to dynamically re-balance networking load of a device using
> an indirection table that is set up in the device. I was wondering if
> this is supported in Linux stack or if anyone is working on that?
It's not supported, but it's on David Miller's to-do list[1].
By the way, Microsoft suddenly decided that RSS is too problematic to
enable by default[2] because software and hardware can disagree about
hash values in the presence of some local NAT implementations.
Hopefully we can avoid that particular pitfall in Linux.
Ben.
1. http://vger.kernel.org/~davem/net_todo.html
2. http://support.microsoft.com/kb/948496
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
next prev parent reply other threads:[~2008-03-12 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 20:51 RFC [PATCH net-2.6 1/6] net: Scheduling softirqs between CPUSs Tom Herbert
2008-03-05 21:21 ` David Miller
2008-03-07 19:02 ` Max Krasnyanskiy
2008-03-10 23:26 ` Tom Herbert
2008-03-11 1:06 ` Brandeburg, Jesse
2008-03-11 16:20 ` Tom Herbert
2008-03-11 16:52 ` Ben Hutchings
2008-03-11 23:48 ` Tom Herbert
2008-03-12 15:10 ` Ben Hutchings [this message]
2008-03-13 3:41 ` David Miller
2008-03-13 11:47 ` Ben Hutchings
2008-03-13 12:53 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080312151051.GI26963@solarflare.com \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=jesse.brandeburg@intel.com \
--cc=maxk@qualcomm.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=therbert@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).