netdev - [PATCH v2 0/3] RSS fix for ixgbe/ixgbevf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1430276261-29821-1-git-send-email-fan.du@intel.com>
Date:	Wed, 29 Apr 2015 10:57:38 +0800
From:	Fan Du <fan.du@...el.com>
To:	jeffrey.t.kirsher@...el.com
Cc:	alexander.h.duyck@...hat.com, emil.s.tantilov@...el.com,
	intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
	Fan Du <fan.du@...el.com>
Subject: [PATCH v2 0/3] RSS fix for ixgbe/ixgbevf

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(-)

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html