From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by dpdk.org (Postfix) with ESMTP id 795FB5F17 for ; Thu, 22 Mar 2018 12:46:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2146; q=dns/txt; s=iport; t=1521719184; x=1522928784; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hfG0yhkImR4bD6eVBitdcRTKvSTjKhKVpGUVnefKz1o=; b=bIdJCCrpK911yp/+jtC67MlRHAIWSyqe/kU5VjQKMEvEUVaOKwGyIqB7 5SCjV8JTHQtE03Y44kMv4RU2DxotfB17erWsv2FQsVQ48HFIdxTknUX/R wWPfF8ik3jbllb6XctbrQECHuSbbS2DFrqVtlcssJZFWu3DRNE1iwMFd/ I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DpAgD/lrNa/4kNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM9gVEoCphegXOBEZJhggYLhQUCg2IhNhYBAgEBAQEBAQJrKIU?= =?us-ascii?q?lAQEBAwEnEz8MBAIBCBEEAQEBHgkHMhQJCAEBBA4FCIR+CKxqNYhBgXuFL4IRg?= =?us-ascii?q?VRAgQyDBopIA5d+CAKOaI0Kj2UCERMBgSQBIwEwgVJwFYJ9giAZjhZvjzoBgRU?= =?us-ascii?q?BAQ?= X-IronPort-AV: E=Sophos;i="5.48,344,1517875200"; d="scan'208";a="87247177" Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Mar 2018 11:46:23 +0000 Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w2MBkNjn014070 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 22 Mar 2018 11:46:23 GMT Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 22 Mar 2018 07:46:22 -0400 Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1320.000; Thu, 22 Mar 2018 07:46:22 -0400 From: "Hanoch Haim (hhaim)" To: Bruce Richardson CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] i40e mbuf->rss indication Thread-Index: AdPBRQrucDZfeSBkRGa2KOwaLov0vwArkoCAAAhR6zA= Date: Thu, 22 Mar 2018 11:46:22 +0000 Message-ID: References: <782383cd531a4248a3634705f46d8acf@XCH-RTP-017.cisco.com> <20180322113457.GB608@bricha3-MOBL.ger.corp.intel.com> In-Reply-To: <20180322113457.GB608@bricha3-MOBL.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [64.103.125.72] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] i40e mbuf->rss indication 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: , X-List-Received-Date: Thu, 22 Mar 2018 11:46:24 -0000 Driver: i40e DPDK : 17.11 Configuration :=20 1) RSS configuration=20 rxmode.mq_mode =3D ETH_MQ_RX_RSS; rss->rss_hf =3D ETH_RSS_UDP | ETH_RSS_TCP; rss->rss_key =3D Microsoft key=20 rss->rss_key_len =3D 52 *configure RETA to some rx-queues 2) Change hash to TOEPLITZ (only for i40e) struct rte_eth_hash_filter_info info =3D {}; info.info_type =3D RTE_ETH_HASH_FILTER_GLOBAL_CONFIG; info.info.global_conf.hash_func =3D RTE_ETH_HASH_FUNCTION_TOEPLIT= Z; rte_eth_dev_filter_ctrl(m_repid,=20 RTE_ETH_FILTER_HASH, RTE_ETH_FILTER_SET, &info); 3) Configure some flow-director rules=20 4) TCP/UDP packets are received to the *right* core (based on a SW Toeplitz= calculation +reta table) however The reported rss value is *wrong* in the mbuf=20 (m->hash.rss =3D=3D *wrong value*) ((m->ol_flags&PKT_RX_RSS_HASH) =3D=3D PKT_RX_RSS_HASH 5) The above works fine for mlx5 and ixgbe 6) I suspect the hash is something else, maybe flow-director id or xor hash= .. Wanted to know if this is a known issue. I can provide a simple way to repr= oduce it using TRex=20 Thanks, Hanoh -----Original Message----- From: Bruce Richardson [mailto:bruce.richardson@intel.com]=20 Sent: Thursday, March 22, 2018 1:35 PM To: Hanoch Haim (hhaim) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] i40e mbuf->rss indication On Wed, Mar 21, 2018 at 06:47:22PM +0000, Hanoch Haim (hhaim) wrote: > Hi All, > DPDK:17.11 > When i40e is configured with RSS enabled and hash.type=3Dtoeplitz >=20 > m->hash.rss =3D some weird number > ((m->ol_flags&PKT_RX_RSS_HASH) =3D=3D PKT_RX_RSS_HASH >=20 > The hash value is correct and match the MS Toeplitz standard. >=20 > Is this expected? I'm sorry, but I don't quite follow the question, or the problem. Are you m= eaning to say that the hash value is incorrect, or that the flag is not bei= ng set or something else? /Bruce >=20 > The above works fine with ixgbe/mlx5 >=20 > Thanks, > Hanoh >=20