From: Ben Hutchings <bhutchings@solarflare.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Jon Zhou <Jon.Zhou@jdsu.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: why all packets have same queue no when rps enabled?
Date: Tue, 22 Feb 2011 13:09:25 +0000 [thread overview]
Message-ID: <1298380165.2211.481.camel@localhost> (raw)
In-Reply-To: <1298379718.2861.3.camel@edumazet-laptop>
On Tue, 2011-02-22 at 14:01 +0100, Eric Dumazet wrote:
> Le mardi 22 février 2011 à 12:45 +0000, Ben Hutchings a écrit :
>
> > The queue number identifies a hardware queue. RPS therefore does not
> > update this number when queueing packets for processing on other CPUs.
> >
> > If the hardware/driver provides a receive hash (probably Toeplitz) then
> > this is used for RPS. Otherwise a much cheaper hash is used.
>
> The default is/should be : rxhash generated in network stack.
>
> ethtool -k eth0 | grep hash
> receive-hashing: off
>
> To use the device/harwdare provided rxhash, you need to ask for it.
>
> ethtool -K eth0 rxhash on
Whether this is enabled by default depends on the driver.
> BTW, I am not sure what you mean by "much cheaper hash is used"...
>
> I presume hardware provided hash is less expensive (for our cpu) than
> computing our rxhash...
I mean the hash function we use is much cheaper than Toeplitz.
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.
prev parent reply other threads:[~2011-02-22 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 4:07 why all packets have same queue no when rps enabled? Jon Zhou
2011-02-22 5:41 ` Eric Dumazet
2011-02-22 5:56 ` Jon Zhou
2011-02-22 6:13 ` Eric Dumazet
2011-02-22 12:45 ` Ben Hutchings
2011-02-22 13:01 ` Eric Dumazet
2011-02-22 13:09 ` Ben Hutchings [this message]
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=1298380165.2211.481.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=Jon.Zhou@jdsu.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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).