[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <305E19FFAC908240AB6DEBD1E2D8C1E17F8289DA@ORSMSX108.amr.corp.intel.com>
Date: Wed, 6 May 2015 22:46:07 +0000
From: "Schmitt, Phillip J" <phillip.j.schmitt@...el.com>
To: "Du, Fan" <fan.du@...el.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Du, Fan" <fan.du@...el.com>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
Subject: RE: [Intel-wired-lan] [PATCH v2 3/3] ixgbe: Don't report flow
director filter's status
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces@...ts.osuosl.org] On
> Behalf Of Fan Du
> Sent: Tuesday, April 28, 2015 7:58 PM
> To: Kirsher, Jeffrey T
> Cc: netdev@...r.kernel.org; Du, Fan; intel-wired-lan@...ts.osuosl.org
> Subject: [Intel-wired-lan] [PATCH v2 3/3] ixgbe: Don't report flow director filter's
> status
>
> For two reasons I want to disable this:
> 1. Not any part actually check the report status(Alexander Duyck) 2. To report
> hash value of a packet to stack,
> RSS -> 32bits hash value
> Perfect match fdir filter -> 13bits hash value
> Hashed-based fdir filter -> 31bits hash value
>
> fdir filter might hash on masked tuples for IP address,
> so it's still not desirable for usage.
>
> So for now, just stick to RSS 32bits hash value.
>
> Signed-off-by: Fan Du <fan.du@...el.com>
> Suggested-by: Alexander Duyck <alexander.h.duyck@...hat.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_82599.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
Tested-by: Phil Schmitt <phillip.j.schmitt@...el.com>
--
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
Powered by blists - more mailing lists