From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vinicius Costa Gomes Date: Fri, 16 Mar 2018 10:59:04 -0700 Subject: [Intel-wired-lan] [next-queue PATCH v4 6/8] igb: Add MAC address support for ethtool nftuple filters In-Reply-To: References: <20180308003713.29195-1-vinicius.gomes@intel.com> <20180308003713.29195-7-vinicius.gomes@intel.com> <309B89C4C689E141A5FF6A0C5FB2118B8C8032A0@ORSMSX101.amr.corp.intel.com> Message-ID: <87muz7vr4n.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: intel-wired-lan@osuosl.org List-ID: Hi, Alexander Duyck writes: > On Tue, Mar 13, 2018 at 8:04 PM, Brown, Aaron F 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 >> 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga18.intel.com ([134.134.136.126]:12465 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752937AbeCPR7G (ORCPT ); Fri, 16 Mar 2018 13:59:06 -0400 From: Vinicius Costa Gomes To: Alexander Duyck , "Brown\, Aaron F" Cc: "intel-wired-lan\@lists.osuosl.org" , "netdev\@vger.kernel.org" , "Sanchez-Palencia\, Jesus" Subject: Re: [Intel-wired-lan] [next-queue PATCH v4 6/8] igb: Add MAC address support for ethtool nftuple filters In-Reply-To: References: <20180308003713.29195-1-vinicius.gomes@intel.com> <20180308003713.29195-7-vinicius.gomes@intel.com> <309B89C4C689E141A5FF6A0C5FB2118B8C8032A0@ORSMSX101.amr.corp.intel.com> Date: Fri, 16 Mar 2018 10:59:04 -0700 Message-ID: <87muz7vr4n.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: netdev-owner@vger.kernel.org List-ID: Hi, Alexander Duyck writes: > On Tue, Mar 13, 2018 at 8:04 PM, Brown, Aaron F 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 >> 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