From: Jeff Garzik <jeff@garzik.org>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Jeff Garzik <jgarzik@redhat.com>,
netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH ethtool 2/2] ethtool: Add support for control of RX flow hash indirection
Date: Fri, 02 Jul 2010 03:25:00 -0400 [thread overview]
Message-ID: <4C2D944C.80604@garzik.org> (raw)
In-Reply-To: <1277910792.2082.18.camel@achroite.uk.solarflarecom.com>
On 06/30/2010 11:13 AM, Ben Hutchings wrote:
> Many NICs use an indirection table to map an RX flow hash value to one
> of an arbitrary number of queues (not necessarily a power of 2). It
> can be useful to remove some queues from this indirection table so
> that they are only used for flows that are specifically filtered
> there. It may also be useful to weight the mapping to account for
> user processes with the same CPU-affinity as the RX interrupts.
>
> Signed-off-by: Ben Hutchings<bhutchings@solarflare.com>
applied 1-2, after making requested printf correction
prev parent reply other threads:[~2010-07-02 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 15:12 [PATCH ethtool 1/2] ethtool-copy.h: sync with net-next Ben Hutchings
2010-06-30 15:13 ` [PATCH ethtool 2/2] ethtool: Add support for control of RX flow hash indirection Ben Hutchings
2010-07-01 16:03 ` Ben Hutchings
2010-07-02 7:25 ` Jeff Garzik [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=4C2D944C.80604@garzik.org \
--to=jeff@garzik.org \
--cc=bhutchings@solarflare.com \
--cc=jgarzik@redhat.com \
--cc=linux-net-drivers@solarflare.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).