From: Andi Kleen <andi@firstfloor.org>
To: Santwona Behera <Santwona.Behera@Sun.COM>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jeff@garzik.org,
Matheos.Worku@Sun.COM, Michael.Speer@Sun.COM,
gkernel-commit@lists.sourceforge.net
Subject: Re: [PATCH 0/3] Add support for rx flow hash configuration in a network device
Date: Sun, 29 Jun 2008 14:17:56 +0200 [thread overview]
Message-ID: <871w2gph8r.fsf@basil.nowhere.org> (raw)
In-Reply-To: <48658078.8030707@Sun.COM> (Santwona Behera's message of "Fri, 27 Jun 2008 17:06:16 -0700")
Santwona Behera <Santwona.Behera@Sun.COM> writes:
> Added new interface to ethtool to configure receive network flow
> classification. This patch adds support for flow distribution using
> hashing where the device can be configured with the fields in the
> receive packet to hash onto one of the multiple Rx rings.
>
> This feature has 3 related patches:
>
> 1. An ethtool application patch.
> 2. A kernel patch for the ethtool interface.
> 3. A kernel patch for the niu driver that implements the ethtool
> config ioctl functions. NOTE: The niu driver already has rx flow
> hashing implemented. With these 3 patches, this feature is now
> configurable using ethtool.
Are you sure ethtool is the right interface for this?
Me thinks the kernel should just do the right thing automatically
for this, by distributing the flows over CPUs.
-Andi
next prev parent reply other threads:[~2008-06-29 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 0:06 [PATCH 0/3] Add support for rx flow hash configuration in a network device Santwona Behera
2008-06-29 12:17 ` Andi Kleen [this message]
2008-06-29 20:49 ` David Miller
2008-06-30 0:15 ` Andi Kleen
2008-07-01 3:33 ` Roland Dreier
2008-07-01 4:42 ` David Miller
2008-07-02 10:50 ` 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=871w2gph8r.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=Matheos.Worku@Sun.COM \
--cc=Michael.Speer@Sun.COM \
--cc=Santwona.Behera@Sun.COM \
--cc=davem@davemloft.net \
--cc=gkernel-commit@lists.sourceforge.net \
--cc=jeff@garzik.org \
--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).