From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 8D596DE3 for ; Fri, 18 Jan 2019 17:26:17 +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 fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jan 2019 08:26:16 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,491,1539673200"; d="scan'208";a="268179254" Received: from irsmsx151.ger.corp.intel.com ([163.33.192.59]) by orsmga004.jf.intel.com with ESMTP; 18 Jan 2019 08:26:15 -0800 Received: from irsmsx156.ger.corp.intel.com (10.108.20.68) by IRSMSX151.ger.corp.intel.com (163.33.192.59) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 18 Jan 2019 16:26:14 +0000 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.213]) by IRSMSX156.ger.corp.intel.com ([169.254.3.156]) with mapi id 14.03.0415.000; Fri, 18 Jan 2019 16:26:14 +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/cFQgAAZIACAABUogIAACJIw Date: Fri, 18 Jan 2019 16:26:13 +0000 Message-ID: <348A99DA5F5B7549AA880327E580B435896CD528@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> In-Reply-To: <5e87ae90-94b9-4e85-9172-46b95365ec36@default> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNmZkYWI5NWYtNzhhNi00MTQ2LWE2NTktZDhiMTZjOGU5ZTgxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiZ3NSSjd6V2hkNlwvQUlCODRpOEY4RVNXaCtqbnNPMVd5SFJGT2V4UU11QWh4WDZaWCs0Tk13WTVmS0tFeWQydVwvIn0= 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 16:26:18 -0000 Hi Alex, > [changchun] In the same thread, but how about to dequeuer at the beginnin= g of the thread each time, > if data presents then processing them, if no data just do other work, and= equeue the packets at some > time but does not wait. > For example: > While(1) > { > Nb_ops =3D dequeuer(); > If(nb_ops > ) > { > process_dequeued_data(); > continue; > } >=20 > Other_work(); > If(ipsec) > Enqueuer(); > } > Does it make sense? [Fiona] It can, though on the first loop ro after a queit time youll proabl= y get very few back on first and second dequeue as It'll be called immediately after the enqueue. Once it gets busy that could= be ok though