From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next-queue PATCH v3 6/8] igb: Add MAC address support for ethtool nftuple filters
Date: Wed, 07 Mar 2018 16:10:38 -0800 [thread overview]
Message-ID: <871sgvzatd.fsf@intel.com> (raw)
In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B8C7FFA86@ORSMSX101.amr.corp.intel.com>
Hi,
"Brown, Aaron F" <aaron.f.brown@intel.com> writes:
>> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
>> Behalf Of Vinicius Costa Gomes
>> Sent: Tuesday, March 6, 2018 5:30 PM
>> To: intel-wired-lan at lists.osuosl.org
>> Cc: netdev at vger.kernel.org; Sanchez-Palencia, Jesus <jesus.sanchez-
>> palencia at intel.com>
>> Subject: [Intel-wired-lan] [next-queue PATCH v3 6/8] igb: Add MAC address
>> support for ethtool nftuple filters
>>
>> This adds the capability of configuring the queue steering of arriving
>> packets based on their source and destination MAC addresses.
>>
>> In practical terms this adds support for the following use cases,
>> characterized by these examples:
>>
>> $ ethtool -N eth0 flow-type ether dst aa:aa:aa:aa:aa:aa action 0
>> (this will direct packets with destination address "aa:aa:aa:aa:aa:aa"
>> to the RX queue 0)
>>
>> $ ethtool -N eth0 flow-type ether src 44:44:44:44:44:44 action 3
>> (this will direct packets with destination address "44:44:44:44:44:44"
>> to the RX queue 3)
>
> I assume this example should read "... source address" rather than
> "...destination".
Ugh, yeah. Will be fixed on v4.
Thank you,
--
Vinicius
WARNING: multiple messages have this Message-ID (diff)
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 v3 6/8] igb: Add MAC address support for ethtool nftuple filters
Date: Wed, 07 Mar 2018 16:10:38 -0800 [thread overview]
Message-ID: <871sgvzatd.fsf@intel.com> (raw)
In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B8C7FFA86@ORSMSX101.amr.corp.intel.com>
Hi,
"Brown, Aaron F" <aaron.f.brown@intel.com> writes:
>> From: Intel-wired-lan [mailto:intel-wired-lan-bounces@osuosl.org] On
>> Behalf Of Vinicius Costa Gomes
>> Sent: Tuesday, March 6, 2018 5:30 PM
>> To: intel-wired-lan@lists.osuosl.org
>> Cc: netdev@vger.kernel.org; Sanchez-Palencia, Jesus <jesus.sanchez-
>> palencia@intel.com>
>> Subject: [Intel-wired-lan] [next-queue PATCH v3 6/8] igb: Add MAC address
>> support for ethtool nftuple filters
>>
>> This adds the capability of configuring the queue steering of arriving
>> packets based on their source and destination MAC addresses.
>>
>> In practical terms this adds support for the following use cases,
>> characterized by these examples:
>>
>> $ ethtool -N eth0 flow-type ether dst aa:aa:aa:aa:aa:aa action 0
>> (this will direct packets with destination address "aa:aa:aa:aa:aa:aa"
>> to the RX queue 0)
>>
>> $ ethtool -N eth0 flow-type ether src 44:44:44:44:44:44 action 3
>> (this will direct packets with destination address "44:44:44:44:44:44"
>> to the RX queue 3)
>
> I assume this example should read "... source address" rather than
> "...destination".
Ugh, yeah. Will be fixed on v4.
Thank you,
--
Vinicius
next prev parent reply other threads:[~2018-03-08 0:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 1:29 [Intel-wired-lan] [next-queue PATCH v3 0/8] igb: offloading of receive filters Vinicius Costa Gomes
2018-03-07 1:29 ` Vinicius Costa Gomes
2018-03-07 1:29 ` [Intel-wired-lan] [next-queue PATCH v3 1/8] igb: Fix not adding filter elements to the list Vinicius Costa Gomes
2018-03-07 1:29 ` Vinicius Costa Gomes
2018-03-07 1:29 ` [Intel-wired-lan] [next-queue PATCH v3 2/8] igb: Fix queue selection on MAC filters on i210 and i211 Vinicius Costa Gomes
2018-03-07 1:29 ` Vinicius Costa Gomes
2018-03-07 1:29 ` [Intel-wired-lan] [next-queue PATCH v3 3/8] igb: Enable the hardware traffic class feature bit for igb models Vinicius Costa Gomes
2018-03-07 1:29 ` Vinicius Costa Gomes
2018-03-07 1:29 ` [Intel-wired-lan] [next-queue PATCH v3 4/8] igb: Add support for MAC address filters specifying source addresses Vinicius Costa Gomes
2018-03-07 1:29 ` Vinicius Costa Gomes
2018-03-07 1:29 ` [Intel-wired-lan] [next-queue PATCH v3 5/8] igb: Enable nfc filters to specify MAC addresses Vinicius Costa Gomes
2018-03-07 1:29 ` Vinicius Costa Gomes
2018-03-07 1:29 ` [Intel-wired-lan] [next-queue PATCH v3 6/8] igb: Add MAC address support for ethtool nftuple filters Vinicius Costa Gomes
2018-03-07 1:29 ` Vinicius Costa Gomes
2018-03-07 22:29 ` [Intel-wired-lan] " Brown, Aaron F
2018-03-07 22:29 ` Brown, Aaron F
2018-03-08 0:10 ` Vinicius Costa Gomes [this message]
2018-03-08 0:10 ` Vinicius Costa Gomes
2018-03-07 1:29 ` [Intel-wired-lan] [next-queue PATCH v3 7/8] igb: Add the skeletons for tc-flower offloading Vinicius Costa Gomes
2018-03-07 1:29 ` Vinicius Costa Gomes
2018-03-07 1:29 ` [Intel-wired-lan] [next-queue PATCH v3 8/8] igb: Add support for adding offloaded clsflower filters Vinicius Costa Gomes
2018-03-07 1:29 ` Vinicius Costa Gomes
2018-03-07 19:48 ` [Intel-wired-lan] " Jakub Kicinski
2018-03-07 19:48 ` Jakub Kicinski
2018-03-07 22:24 ` [Intel-wired-lan] " Vinicius Costa Gomes
2018-03-07 22:24 ` 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=871sgvzatd.fsf@intel.com \
--to=vinicius.gomes@intel.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.