From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next-queue PATCH v4 6/8] igb: Add MAC address support for ethtool nftuple filters
Date: Fri, 16 Mar 2018 10:59:04 -0700 [thread overview]
Message-ID: <87muz7vr4n.fsf@intel.com> (raw)
In-Reply-To: <CAKgT0Uf3MmMRELo0c11Aqah92+shLFASzPkZxE6OzGU5bjvzfA@mail.gmail.com>
Hi,
Alexander Duyck <alexander.duyck@gmail.com> writes:
> On Tue, Mar 13, 2018 at 8:04 PM, Brown, Aaron F <aaron.f.brown@intel.com> wrote:
>>> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
>>> Behalf Of Vinicius Costa Gomes
>>> Sent: Wednesday, March 7, 2018 4:37 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 v4 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 source address "44:44:44:44:44:44" to
>>> the RX queue 3)
>>
>> This seems to work fine on i210, and the patch series allows me to set the rx filters on the i350, i354 and i211, but it is not directing the packets to the queue I request.
>>
>> With the exception of i210 the rx_queues number does not seem to be effected by setting the filter. In the case of i211 the rx packets stay on rx_queue 0 with or without an ether src or dst filter. The first example one seems to work at first since it's directing to queue 0, but changing the filter to "action 1" does not change the behavior. With the i350 and i354 ports the packets are spread across the rx_queues with or without the filter set.
>
> Do any of the other parts actually support this functionality? I don't
> think they do.
From what I can see, the only other part that supports queue steering (by MAC
addresses) is the 82575. But as I don't have any of those handy, making
it work only for the i210 seems more reasonable, to avoid getting into
this situation again.
>
> What we might look at doing instead of trying to add support for other
> parts would be to explicitly limit this functionality to the i210
> since if I am not mistaken this may be a feature only available in
> that hardware.
Sounds good to me.
>
> Thanks.
>
> - Alex
Cheers,
--
Vinicius
WARNING: multiple messages have this Message-ID (diff)
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Alexander Duyck <alexander.duyck@gmail.com>, "Brown\,
Aaron F" <aaron.f.brown@intel.com>
Cc: "intel-wired-lan\@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
"Sanchez-Palencia\, Jesus" <jesus.sanchez-palencia@intel.com>
Subject: Re: [Intel-wired-lan] [next-queue PATCH v4 6/8] igb: Add MAC address support for ethtool nftuple filters
Date: Fri, 16 Mar 2018 10:59:04 -0700 [thread overview]
Message-ID: <87muz7vr4n.fsf@intel.com> (raw)
In-Reply-To: <CAKgT0Uf3MmMRELo0c11Aqah92+shLFASzPkZxE6OzGU5bjvzfA@mail.gmail.com>
Hi,
Alexander Duyck <alexander.duyck@gmail.com> writes:
> On Tue, Mar 13, 2018 at 8:04 PM, Brown, Aaron F <aaron.f.brown@intel.com> wrote:
>>> From: Intel-wired-lan [mailto:intel-wired-lan-bounces@osuosl.org] On
>>> Behalf Of Vinicius Costa Gomes
>>> Sent: Wednesday, March 7, 2018 4:37 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 v4 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 source address "44:44:44:44:44:44" to
>>> the RX queue 3)
>>
>> This seems to work fine on i210, and the patch series allows me to set the rx filters on the i350, i354 and i211, but it is not directing the packets to the queue I request.
>>
>> With the exception of i210 the rx_queues number does not seem to be effected by setting the filter. In the case of i211 the rx packets stay on rx_queue 0 with or without an ether src or dst filter. The first example one seems to work at first since it's directing to queue 0, but changing the filter to "action 1" does not change the behavior. With the i350 and i354 ports the packets are spread across the rx_queues with or without the filter set.
>
> Do any of the other parts actually support this functionality? I don't
> think they do.
>From what I can see, the only other part that supports queue steering (by MAC
addresses) is the 82575. But as I don't have any of those handy, making
it work only for the i210 seems more reasonable, to avoid getting into
this situation again.
>
> What we might look at doing instead of trying to add support for other
> parts would be to explicitly limit this functionality to the i210
> since if I am not mistaken this may be a feature only available in
> that hardware.
Sounds good to me.
>
> Thanks.
>
> - Alex
Cheers,
--
Vinicius
next prev parent reply other threads:[~2018-03-16 17:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 0:37 [Intel-wired-lan] [next-queue PATCH v3 0/8] igb: offloading of receive filters Vinicius Costa Gomes
2018-03-08 0:37 ` Vinicius Costa Gomes
2018-03-08 0:37 ` [Intel-wired-lan] [next-queue PATCH v4 1/8] igb: Fix not adding filter elements to the list Vinicius Costa Gomes
2018-03-08 0:37 ` Vinicius Costa Gomes
2018-03-08 0:37 ` [Intel-wired-lan] [next-queue PATCH v4 2/8] igb: Fix queue selection on MAC filters on i210 and i211 Vinicius Costa Gomes
2018-03-08 0:37 ` Vinicius Costa Gomes
2018-03-14 3:07 ` [Intel-wired-lan] " Brown, Aaron F
2018-03-14 3:07 ` Brown, Aaron F
2018-03-14 17:25 ` Vinicius Costa Gomes
2018-03-14 17:25 ` Vinicius Costa Gomes
2018-03-08 0:37 ` [Intel-wired-lan] [next-queue PATCH v4 3/8] igb: Enable the hardware traffic class feature bit for igb models Vinicius Costa Gomes
2018-03-08 0:37 ` Vinicius Costa Gomes
2018-03-08 0:37 ` [Intel-wired-lan] [next-queue PATCH v4 4/8] igb: Add support for MAC address filters specifying source addresses Vinicius Costa Gomes
2018-03-08 0:37 ` Vinicius Costa Gomes
2018-03-08 0:37 ` [Intel-wired-lan] [next-queue PATCH v4 5/8] igb: Enable nfc filters to specify MAC addresses Vinicius Costa Gomes
2018-03-08 0:37 ` Vinicius Costa Gomes
2018-03-08 0:37 ` [Intel-wired-lan] [next-queue PATCH v4 6/8] igb: Add MAC address support for ethtool nftuple filters Vinicius Costa Gomes
2018-03-08 0:37 ` Vinicius Costa Gomes
2018-03-14 3:04 ` [Intel-wired-lan] " Brown, Aaron F
2018-03-14 3:04 ` Brown, Aaron F
2018-03-14 19:58 ` Vinicius Costa Gomes
2018-03-14 19:58 ` Vinicius Costa Gomes
2018-03-16 17:38 ` Alexander Duyck
2018-03-16 17:38 ` Alexander Duyck
2018-03-16 17:59 ` Vinicius Costa Gomes [this message]
2018-03-16 17:59 ` Vinicius Costa Gomes
2018-03-16 18:07 ` Alexander Duyck
2018-03-16 18:07 ` Alexander Duyck
2018-03-16 18:14 ` Brown, Aaron F
2018-03-16 18:14 ` Brown, Aaron F
2018-03-08 0:37 ` [Intel-wired-lan] [next-queue PATCH v4 7/8] igb: Add the skeletons for tc-flower offloading Vinicius Costa Gomes
2018-03-08 0:37 ` Vinicius Costa Gomes
2018-03-08 0:37 ` [Intel-wired-lan] [next-queue PATCH v4 8/8] igb: Add support for adding offloaded clsflower filters Vinicius Costa Gomes
2018-03-08 0:37 ` 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=87muz7vr4n.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.