From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sonic317-55.consmr.mail.bf2.yahoo.com (sonic317-55.consmr.mail.bf2.yahoo.com [74.6.129.110]) by dpdk.org (Postfix) with ESMTP id 0BC882A6A for ; Thu, 17 Jan 2019 23:36:48 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1547764608; bh=k1BeioZ/6AphWnmLV22Arp0EV5Wlq6DwojU5+ALJvsQ=; h=Date:From:To:Subject:References:From:Subject; b=iF3nHgYNZeCCpLArCUxF9MMqKcq1dpGD7bbEgJEGch5tRp2VhX+ErsP29CfkSSVGOWXqd7WFAzflyM3CGe6qDivq56YZ5UsGz4q8k3+Z5poHFZ0a9lZ8N5wQM6xl8CETsaYHeFT/+YB0QfM2ugXGcN3JCqI+hGZ0KjW2oMfgUuFwcTdBSxd7JjecvNCOX01uv+upPCHlnrjtUJjlaB1+drQdGuQmJjhpBYNE5IG51VN8e/FSpQTMpplQySX/vIVnkM/EH9Wpx35Sb/WiCQt4U3+Yk1q0F/BbqklSPD8PcCh3wMy9HQMKxevVc4UVrPuprzuPtB9nwZTxXb7bZLt5bA== X-YMail-OSG: .yVkf8EVM1kLVsy1V8xMOF4wnDuxPw_Qx3YfMOF74XdwKW4ir8MYswaKZVTLR_6 ANgMM0GgmZzWXBqhPTQmU6Fzl7nsmonjVulGXV5fMLZ9qWhtjcXKaAUB.xwlTgba4KbOE4mOWMqD fqQiULoZAM4X0Sm5KSeyNBrLl4UsV2c_wlsMGXyFb47RATVJHCHIusGR2_pZcqML.FIX9V2pU48f gsJfMKl0dqwONS55EdGhrW6MgriaLGGDNRAy6d1cRrXYzpTOS884_hfxvaWRBgxCKEEvXK7U0Flv bphZAzaUtSgw2qAQdk3sKYiL.r6xJwgqwPojfnyMBNB5PhlvRlQN2vvjCrEmXNfqVg5x2lNO8Uan xL1IbL4_MR1he8R7cSSqi45O92VyW7LC4FSZOoZPT4._gCBM4TmNAaNNl1CAbhTml0sck7DfKGpr dPdPkyDxoC589btDx63F_Fa35F1IopmgIs8Smt4QS6WLlhvlDE27bmv2JI_P_gywDULOrVDRFk3T d8v1flOympcb_PDHW6H7vSU3M4Yzt2h7qaDLDp5Mi2F0lXjlJ9hCDXdfy37JP2LWcvc.ZbMl7MUD 1do7RYPxcc0CGxxbJTwaJyCduzVcQHqLuCtPfpXWOsJwD3q9x3Iu7R92L2exiuvLtgujrFkeTuoX JgEJQP92ljwRU2Y7ATnjB_mid42w8btMQGacqhLpuaHwu5kdTRKNrmAJTLPnV2PLqiXb56FrY3Lf .ocSTgcHNoK024qH1nN3fnsxKKYaZNFX7q2ykXB6AIafO.pmRe1Il0RsP5zf7WSsF7qBZGeC5wVQ 8.X5CYn2OPyqks2FAE9DBt6NmmzdB9pzud12eOszIkJMTIPDQc2x4ufZlLA5.MwpaP94PBaGdTxx evuGzI9Zaq0e__6YhsAVQaMXn_ssXwLsUPsqTXThSIUnSIiQhLckASvpFc_ZbKJso9jAltQ3nOcL PNCVBvncx3zZoNcM3mbbNDcc..2XdznauG88VX24f.0oF9fofJP3Fa2zajm817ef1oc9E2wACRaO 0..5A.195biJfxelzqSW4Dvtl3COX3hvr3lGiAOQ- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.bf2.yahoo.com with HTTP; Thu, 17 Jan 2019 22:36:48 +0000 Date: Thu, 17 Jan 2019 22:34:47 +0000 (UTC) From: A-three Mpt To: "users@dpdk.org" Message-ID: <114275557.1446871.1547764487314@mail.yahoo.com> MIME-Version: 1.0 References: <114275557.1446871.1547764487314.ref@mail.yahoo.com> X-Mailer: WebService/1.1.12857 YMailNorrin Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 X-Mailman-Approved-At: Sat, 19 Jan 2019 00:15:55 +0100 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] x710 (i40e) hash set up questions X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2019 22:36:49 -0000 Hi, I am having trouble to understand x710 hash setup. Is my following understa= nding right? =20 - Q1: We select a generic flow type and it will be convert to NIC-depend= ent pctype, right? - =20 Q2: What is the hash_inset? e.g., in the document:=C2=A0For example, to use= only 48bit prefix for IPv6 src address for IPv6 TCP RSS: testpmd> port config 0 pctype 43 hash_inset clear all testpmd> port config 0 pctype 43 hash_inset set field 13 testpmd> port config 0 pctype 43 hash_inset set field 14 testpmd> port config 0 pctype 43 hash_inset set field 15 =20 I found pctype 43 is=C2=A0NonFIPV6, TCP=C2=A0from the data sheet, but how a= re the field 13, 14, 15 related to the 48 bit prefix of src address? - Q3: There are generic functions like=C2=A0rte_eth_dev_filter_ctrl()=C2= =A0and i40e-specific ones like=C2=A0rte_pmd_i40e_inset_set. Do I need both = of them to work? Any relations between them? - Q4: If I want to hash based on the new pctype added (22 to 25 for GTPU= and GTPC), how can I do that? - If I config 4 queues on a port, how can I set up the RSS to distribute= pctype 22 and 23 to these 4 queues? Thanks very much,Athree >From fiona.trahe@intel.com Mon Jan 21 19:52:06 2019 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 5DED15B40 for ; Mon, 21 Jan 2019 19:52:06 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Jan 2019 10:52:04 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,503,1539673200"; d="scan'208";a="129557222" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by orsmga001.jf.intel.com with ESMTP; 21 Jan 2019 10:52:04 -0800 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.213]) by IRSMSX153.ger.corp.intel.com ([169.254.9.115]) with mapi id 14.03.0415.000; Mon, 21 Jan 2019 18:52:03 +0000 From: "Trahe, Fiona" To: Changchun Zhang , "Pathak, Pravin" , "users@dpdk.org" CC: "Trahe, Fiona" Thread-Topic: [dpdk-users] Run-to-completion or Pipe-line for QAT PMD in DPDK Thread-Index: AQHUrriXjo1+JKJBjkaH5GQU9xCtbKW0/cFQgAAZIACAABUogIAACJIwgAAHYoCAAAGjsIAAExAAgAADhJCAAAxnAIAABH9Q Date: Mon, 21 Jan 2019 18:52:02 +0000 Message-ID: <348A99DA5F5B7549AA880327E580B435896CEEE9@IRSMSX101.ger.corp.intel.com> References: <03fd164b-112b-4e44-a5b0-15c6e3703662@default> <348A99DA5F5B7549AA880327E580B435896CD08F@IRSMSX101.ger.corp.intel.com> <168A68C163D584429EF02A476D5274424DEA9B7C@FMSMSX108.amr.corp.intel.com> <5e87ae90-94b9-4e85-9172-46b95365ec36@default> <348A99DA5F5B7549AA880327E580B435896CD528@IRSMSX101.ger.corp.intel.com> <400475b7-869e-4281-9d31-058f96957fe1@default> <348A99DA5F5B7549AA880327E580B435896CD61A@IRSMSX101.ger.corp.intel.com> <348A99DA5F5B7549AA880327E580B435896CD7E0@IRSMSX101.ger.corp.intel.com> In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMTRmMzBlYjMtNzdlMi00NWE3LTk5M2MtYTAzMTk3OWM2NWExIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiczA1NDUxVkRzZTV1bndTTlBWQkhSYUU2SnkzYkFlbjZRYkw2R2UrXC9DU1NEXC9Lb2Ywa0xpU1I4R29BM3NDWjN3In0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] Run-to-completion or Pipe-line for QAT PMD in DPDK X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2019 18:52:06 -0000 > -----Original Message----- > From: Changchun Zhang [mailto:changchun.zhang@oracle.com] > Sent: Friday, January 18, 2019 6:53 PM > To: Trahe, Fiona ; Pathak, Pravin ; > users@dpdk.org > Subject: RE: [dpdk-users] Run-to-completion or Pipe-line for QAT PMD in D= PDK >=20 > HI Fiona, >=20 > Thanks! > Changchun (Alex) >=20 >=20 > -----Original Message----- > From: Trahe, Fiona [mailto:fiona.trahe@intel.com] > Sent: Friday, January 18, 2019 1:21 PM > To: Changchun Zhang ; Pathak, Pravin ; > users@dpdk.org > Cc: Trahe, Fiona > Subject: RE: [dpdk-users] Run-to-completion or Pipe-line for QAT PMD in D= PDK >=20 > Hi Alex, >=20 > > [changchun] Many thanks! So from this limitation, we can conclude > > that Lcore can only dequeue the QAT queue which was enqueued by > > itself, right. If so, then the Crypto device lib doc may be a little mi= sleading, at least some notes > should be put there. > [Fiona] Limitations are generally on the device documentation - it wouldn= 't make sense to pollute the > lib with the limitations of individual devices. (though I understand it's= easy to miss the limitations) As > mentioned before, if this is an important use-case for you we would be in= terested in hearing about it, > and we could investigate performant ways to remove the limitation. >=20 > [changchun] Currently we don't see if it is necessary to remove this lim= itation or not. But we do need > to confirm what the relationship between logical core, queue pair, and cr= ypto device. As my > understanding, no matter pipe line or current limitation, the QAT accepts= the request from the RX > queue of a queue pair and after the processing, the data will be put the = TX queue on the same queue > pair, it is right? Say enqueue data to the RX queue of Queue pair 1, the = return data would always be > put to the TX queue of Queue pair 1, not possible to other Queue pair's T= X queue, right? Let me know > if you did not get my question. [Fiona] well, we use names tx and rx the opposite way you named them - but = this doesn't matter as neither tx nor rx names are visible on the API. Just qp_id. So whatever qp_id you e= nqueue to, you will get the response on the same qp_id in a subsequent dequeue operation. And they will be deque= ued in same order as you enqueued. =20