netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: "Brown\, Aaron F" <aaron.f.brown@intel.com>,
	"intel-wired-lan\@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>
Cc: "netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
	"Sanchez-Palencia\, Jesus" <jesus.sanchez-palencia@intel.com>
Subject: RE: [Intel-wired-lan] [next-queue PATCH v5 7/9] igb: Add MAC address support for ethtool nftuple filters
Date: Mon, 26 Mar 2018 16:55:39 -0700	[thread overview]
Message-ID: <87lgeecryc.fsf@intel.com> (raw)
In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B8C81BBB3@ORSMSX101.amr.corp.intel.com>

Hi Aaron,

"Brown, Aaron F" <aaron.f.brown@intel.com> writes:

>
> Maybe not "this" patch, but this is the one that enables the ethtool commands, so replying here.
> The filters do not seem to take effect with this version (v5) of the
> series.  The commands are accepted for i210 and rejected with
> unsupported messages for the other adapters (as desired) and an
> ethtool -n shows the filter, however, with either the src or dst
> filter set I can run traffic (netperf) that should be caught by the
> filter and rather than being directed to the single queue it is spread
> across queues as would be expected without the filter set.
>
> The test system still has a kernel / driver with the v4 series of this
> patch set and the exact same filter commands / system setup does
> filter the traffic to the specified rx queue with the v4 series.

That's interesting. The only difference is that now non steering filters
(filters added by 'ip (m)addr', PACKET_ADD_MEMBERSHIP and the local MAC
address, for example) do not have the QSEL bit set.

On my tests I cannot detect any change in behaviour between those two
versions of the series, for example. trying to add a filter for the
local MAC address has no visible effect in both versions. (This raises a
question: should this be an error, or should this override the default
entry configuration, or this behaviour is fine?)

Can you share more information about your tests? so I can reproduce it here.


Thank you,

  reply	other threads:[~2018-03-26 23:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22  0:33 [next-queue PATCH v5 0/9] igb: offloading of receive filters Vinicius Costa Gomes
2018-03-22  0:33 ` [next-queue PATCH v5 1/9] igb: Fix not adding filter elements to the list Vinicius Costa Gomes
2018-03-22  0:33 ` [next-queue PATCH v5 2/9] igb: Fix queue selection on MAC filters on i210 Vinicius Costa Gomes
2018-03-22  0:33 ` [next-queue PATCH v5 3/9] igb: Enable the hardware traffic class feature bit for igb models Vinicius Costa Gomes
2018-03-22  0:33 ` [next-queue PATCH v5 4/9] igb: Add support for MAC address filters specifying source addresses Vinicius Costa Gomes
2018-03-22  0:33 ` [next-queue PATCH v5 5/9] igb: Add support for enabling queue steering in filters Vinicius Costa Gomes
2018-03-22  0:33 ` [next-queue PATCH v5 6/9] igb: Enable nfc filters to specify MAC addresses Vinicius Costa Gomes
2018-03-22  0:33 ` [next-queue PATCH v5 7/9] igb: Add MAC address support for ethtool nftuple filters Vinicius Costa Gomes
2018-03-24  3:40   ` [Intel-wired-lan] " Brown, Aaron F
2018-03-26 23:55     ` Vinicius Costa Gomes [this message]
2018-03-27  1:40       ` Brown, Aaron F
2018-03-28  0:12         ` Vinicius Costa Gomes
2018-03-22  0:33 ` [next-queue PATCH v5 8/9] igb: Add the skeletons for tc-flower offloading Vinicius Costa Gomes
2018-03-22  0:33 ` [next-queue PATCH v5 9/9] igb: Add support for adding offloaded clsflower filters Vinicius Costa Gomes

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=87lgeecryc.fsf@intel.com \
    --to=vinicius.gomes@intel.com \
    --cc=aaron.f.brown@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesus.sanchez-palencia@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).