From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 0F0C81150 for ; Fri, 18 Jan 2019 19:20:57 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jan 2019 10:20:57 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,491,1539673200"; d="scan'208";a="268211109" Received: from irsmsx105.ger.corp.intel.com ([163.33.3.28]) by orsmga004.jf.intel.com with ESMTP; 18 Jan 2019 10:20:56 -0800 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.213]) by irsmsx105.ger.corp.intel.com ([169.254.7.116]) with mapi id 14.03.0415.000; Fri, 18 Jan 2019 18:20:55 +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/cFQgAAZIACAABUogIAACJIwgAAHYoCAAAGjsIAAExAAgAADhJA= Date: Fri, 18 Jan 2019 18:20:54 +0000 Message-ID: <348A99DA5F5B7549AA880327E580B435896CD7E0@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> 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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiY2ViODViMzEtNGQwOC00YWM0LWI3MzgtYTRkZGZlOGZjODViIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiendWOEtUcHMwUjBoTFM5QXpZVGdqRXJGNXlyck5GclFlZGFrRVh1M0RyNG1cL1wvQXVVZ3BiK2gwV0srNXExS0pZIn0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [163.33.239.181] 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: Fri, 18 Jan 2019 18:20:58 -0000 Hi Alex, > [changchun] Many thanks! So from this limitation, we can conclude that L= core can only dequeue the > QAT queue which was enqueued by itself, right. If so, then the Crypto dev= ice lib doc may be a little > misleading, 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 i= nterested in hearing about it, and we could investigate performant ways to remove the limitation.