From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2735DA0613 for ; Wed, 31 Jul 2019 04:58:07 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 982F51C00D; Wed, 31 Jul 2019 04:58:05 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 997231C000 for ; Wed, 31 Jul 2019 04:58:03 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jul 2019 19:58:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,328,1559545200"; d="scan'208";a="177139442" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by orsmga006.jf.intel.com with ESMTP; 30 Jul 2019 19:58:01 -0700 Received: from fmsmsx116.amr.corp.intel.com (10.18.116.20) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 30 Jul 2019 19:58:00 -0700 Received: from shsmsx105.ccr.corp.intel.com (10.239.4.158) by fmsmsx116.amr.corp.intel.com (10.18.116.20) with Microsoft SMTP Server (TLS) id 14.3.439.0; Tue, 30 Jul 2019 19:58:00 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.112]) by SHSMSX105.ccr.corp.intel.com ([169.254.11.15]) with mapi id 14.03.0439.000; Wed, 31 Jul 2019 10:57:58 +0800 From: "Su, Simei" To: Stephen Hemminger CC: "Zhang, Qi Z" , "Wu, Jingjing" , "adrien.mazarguil@6wind.com" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [RFC,v2] ethdev: extend RSS offload types Thread-Index: AQHVQ1AZk+YyZjDxeUygmsS7F7LbkKbi0C+AgAE/8sA= Date: Wed, 31 Jul 2019 02:57:57 +0000 Message-ID: <65F28F834D25B54B9EC1999B623071B30C4291FA@SHSMSX104.ccr.corp.intel.com> References: <1564054620-43179-1-git-send-email-simei.su@intel.com> <1564101350-98092-1-git-send-email-simei.su@intel.com> <20190730085007.23775125@hermes.lan> In-Reply-To: <20190730085007.23775125@hermes.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.600.7 dlp-reaction: no-action x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiY2FlNDAwMWYtZDM4YS00YzJhLTlmNWYtZTMxMGMwNTdkNTM1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiV2FwNWR3UFhZVDVKVTBpdGprSnl3MFVQUTczMHNJN0JVOEgrcU9MSk5PZXQyQU03U2w1YlhwdlwvNVZ1b284NkEifQ== x-ctpclassification: CTP_NT x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [RFC,v2] ethdev: extend RSS offload types X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > -----Original Message----- > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > Sent: Tuesday, July 30, 2019 11:50 PM > To: Su, Simei > Cc: Zhang, Qi Z ; Wu, Jingjing ; > adrien.mazarguil@6wind.com; dev@dpdk.org > Subject: Re: [dpdk-dev] [RFC,v2] ethdev: extend RSS offload types >=20 > On Fri, 26 Jul 2019 08:35:50 +0800 > simei wrote: >=20 > > From: Simei Su > > > > This RFC reserves several bits as input set selection from bottom of > > the 64 bits. The flow type is combined with input set to represent rss > > types. > > > > Correct the input set mask to align with the definition in rte_ethdev.h= . > > for example: > > ETH_RSS_IPV4 | ETH_RSS_INSET_L3_SRC: hash on src ip address only > > ETH_RSS_IPV4_UDP | ETH_RSS_INSET_L4_DST: hash on src/dst IP and > > dst UDP port > > ETH_RSS_L2_PAYLOAD | ETH_RSS_INSET_L2_DST: hash on dst mac > address > > > > Signed-off-by: Simei Su >=20 > NAK to any patch that "reserves" bits for future use. >=20 > Please include the patch as part of a set of patches that actually implem= ents the > functionality on a device. =20 Ok. Later, I will add the implementation functionality as a set of patche= s.