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 C71FB34F2 for ; Thu, 22 Mar 2018 13:28:01 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Mar 2018 05:27:50 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,344,1517904000"; d="scan'208";a="213664001" Received: from irsmsx109.ger.corp.intel.com ([163.33.3.23]) by fmsmga006.fm.intel.com with ESMTP; 22 Mar 2018 05:27:49 -0700 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.216]) by IRSMSX109.ger.corp.intel.com ([169.254.13.170]) with mapi id 14.03.0319.002; Thu, 22 Mar 2018 12:27:49 +0000 From: "Ananyev, Konstantin" To: "Zhang, Qi Z" , "dev@dpdk.org" CC: "thomas@monjalon.net" Thread-Topic: Question for queue_start Thread-Index: AdPB1w6NvRoZyKOLTZC8kG/sZZ923AAAdStA Date: Thu, 22 Mar 2018 12:27:48 +0000 Message-ID: <2601191342CEEE43887BDE71AB977258A0AB30B1@irsmsx105.ger.corp.intel.com> References: <039ED4275CED7440929022BC67E7061153171181@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <039ED4275CED7440929022BC67E7061153171181@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMjYwYjBmZDktN2M3ZS00ZmUwLWE2OTktMTg0OWFhNTc4M2ZjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IjhMRyt1c09jNGhCeGNcLzVrRmE5dkZpRWg3Z05pZmM5bzIwd0ErQm9wZjI4PSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Question for queue_start 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 12:28:02 -0000 Hi Qi,=20 >Hi: >=A0=A0=A0=A0=A0=A0 In rte_eth_dev_rx|tx_queue_start, dev_started is not ch= ecked >=A0=A0=A0=A0=A0=A0=A0=A0=20 >=A0=A0=A0=A0=A0 Which mean we can call =A0 >=A0=A0=A0=A0=A0=A0=A0=A0 Rte_eth_rx_queue_setup >=A0=A0=A0=A0=A0=A0=A0=A0 Rte_eth_rx_qeueu_start=A0=A0=A0=A0=A0=A0=A0=A0=20 > >=A0=A0=A0=A0=A0=A0=A0=A0 And what we expected is the queue is started whil= e device is still stopped, does this make sense? >=A0=A0=A0=A0=A0=A0=A0=A0 Should it return fail when device is not started? Good point, I think we should. Konstantin > >Thanks >Qi