From: "Schmitt, Phillip J" <phillip.j.schmitt@intel.com>
To: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Du, Fan" <fan.du@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: RE: [Intel-wired-lan] [PATCH v2 0/3] RSS fix for ixgbe/ixgbevf
Date: Wed, 6 May 2015 19:47:42 +0000 [thread overview]
Message-ID: <305E19FFAC908240AB6DEBD1E2D8C1E17F8287BF@ORSMSX108.amr.corp.intel.com> (raw)
In-Reply-To: <1430398781.2669.110.camel@jtkirshe-mobl>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces@lists.osuosl.org] On
> Behalf Of Jeff Kirsher
> Sent: Thursday, April 30, 2015 6:00 AM
> To: Du, Fan
> Cc: netdev@vger.kernel.org; intel-wired-lan@lists.osuosl.org
> Subject: Re: [Intel-wired-lan] [PATCH v2 0/3] RSS fix for ixgbe/ixgbevf
>
> On Wed, 2015-04-29 at 10:57 +0800, Fan Du wrote:
> > This patchset provides RSS hash value for upper stack by indicating
> > whether it's a L3 or L4 hash. Thus other component of network stack
> > could utilize this hash value provided by NIC without caculating by
> > themselves.
> >
> > Test:
> > * Simple iperf test using ixgbe for 82599ES
> > * Build test only for ixgbevf
> > * make C=1 CF=-D__CHECK_ENDIAN__, no warnings introduced by this
> > patchset
> >
> > Changelog:
> > v2:
> > - Add patch3 to make all hash value from RSS part.
> > v1:
> > - Code style issue suggeted by Tantilov, Emil S.
> > - Initial version
> >
> > Fan Du (3):
> > ixgbe: Specify rx hash type wrt rx desc RSS type
> > ixgbevf: Set rx hash type for ingress packets
> > ixgbe: Don't report flow director filter's status
> >
> > drivers/net/ethernet/intel/ixgbe/ixgbe_82599.c | 2 -
> > drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 25 ++++++++++++++++---
> > drivers/net/ethernet/intel/ixgbevf/defines.h | 12 +++++++++
> > drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 27
> +++++++++++++++++++++
> > 4 files changed, 60 insertions(+), 6 deletions(-)
> >
>
> Thanks Fan, I have added your series to my queue for further review and testing.
Tested-by: Phil Schmitt <phillip.j.schmitt@intel.com>
prev parent reply other threads:[~2015-05-06 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 2:57 [PATCH v2 0/3] RSS fix for ixgbe/ixgbevf Fan Du
2015-04-29 2:57 ` [PATCH v2 1/3] ixgbe: Specify rx hash type wrt rx desc RSS type Fan Du
2015-05-06 22:45 ` [Intel-wired-lan] " Schmitt, Phillip J
2015-04-29 2:57 ` [PATCH v2 2/3] ixgbevf: Set rx hash type for ingress packets Fan Du
2015-05-06 22:45 ` [Intel-wired-lan] " Schmitt, Phillip J
2015-04-29 2:57 ` [PATCH v2 3/3] ixgbe: Don't report flow director filter's status Fan Du
2015-05-06 22:46 ` [Intel-wired-lan] " Schmitt, Phillip J
2015-04-30 12:59 ` [PATCH v2 0/3] RSS fix for ixgbe/ixgbevf Jeff Kirsher
2015-05-06 19:47 ` Schmitt, Phillip J [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=305E19FFAC908240AB6DEBD1E2D8C1E17F8287BF@ORSMSX108.amr.corp.intel.com \
--to=phillip.j.schmitt@intel.com \
--cc=fan.du@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.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).