From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vinicius Costa Gomes Date: Wed, 07 Mar 2018 16:10:38 -0800 Subject: [Intel-wired-lan] [next-queue PATCH v3 6/8] igb: Add MAC address support for ethtool nftuple filters In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B8C7FFA86@ORSMSX101.amr.corp.intel.com> References: <20180307012957.7052-1-vinicius.gomes@intel.com> <20180307012957.7052-7-vinicius.gomes@intel.com> <309B89C4C689E141A5FF6A0C5FB2118B8C7FFA86@ORSMSX101.amr.corp.intel.com> Message-ID: <871sgvzatd.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, "Brown, Aaron F" 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 > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com ([134.134.136.20]:22334 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932448AbeCHAKj (ORCPT ); Wed, 7 Mar 2018 19:10:39 -0500 From: Vinicius Costa Gomes To: "Brown\, Aaron F" , "intel-wired-lan\@lists.osuosl.org" Cc: "netdev\@vger.kernel.org" , "Sanchez-Palencia\, Jesus" Subject: RE: [Intel-wired-lan] [next-queue PATCH v3 6/8] igb: Add MAC address support for ethtool nftuple filters In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B8C7FFA86@ORSMSX101.amr.corp.intel.com> References: <20180307012957.7052-1-vinicius.gomes@intel.com> <20180307012957.7052-7-vinicius.gomes@intel.com> <309B89C4C689E141A5FF6A0C5FB2118B8C7FFA86@ORSMSX101.amr.corp.intel.com> Date: Wed, 07 Mar 2018 16:10:38 -0800 Message-ID: <871sgvzatd.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: netdev-owner@vger.kernel.org List-ID: Hi, "Brown, Aaron F" 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 > 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