From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id AC3485593 for ; Thu, 22 Mar 2018 13:59:57 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E5C3D211E1; Thu, 22 Mar 2018 08:59:56 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 22 Mar 2018 08:59:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=xYpor7LB2TP8L5GSb8w/kR3QBe LgP/yehf0Q5jaItDc=; b=WDeerMglUI4DBa6KyF9p8UJrVkQtlUgAFU0CbxSaZF ldEyzuX207NwoXyAuOsOc0/HD04kuTezInmB2RoqxPHvtLE/jUc/t9KO4ouyZ+ws UGWK1fq9mb1KVTwx4uEBqlmkQYdwVo7/6tD34ynbF+sjOefKKRiIwXuGBm5/TULc A= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=xYpor7 LB2TP8L5GSb8w/kR3QBeLgP/yehf0Q5jaItDc=; b=W1krWVkvPgco+buyPUn+2b i84zpvyB3ZXQSasRfFrKoOTlR7hPshG5mXvgtOUSWMN+eM1qJNLpgAWEi3EfJZpK vVwAfGJX3aH3Bn++iqE912qPoD6LrYBBXvJK2dipQQTrU2q8joEbt17sVmKb3QtD kGtPeRHPVbobLssqI87TyCxwpzrPoM7KmBti1jxgrvrMmhatOZ81wGyORACJ0nJT MgMbAbWMUiPSciccQq3Qu8N2/drfwCEw24DCPH28IBOTZNA0pOVY205Xu65ldgNe kiVa/nQU7k5aKz8AS9h2PIkIr6yqGuc/UY5b3XCW0hXtKDdEp7ouueZuHr5zwC2Q == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 639E47E1A2; Thu, 22 Mar 2018 08:59:56 -0400 (EDT) From: Thomas Monjalon To: "Ananyev, Konstantin" Cc: "Zhang, Qi Z" , "dev@dpdk.org" Date: Thu, 22 Mar 2018 13:59:55 +0100 Message-ID: <2293021.YCkHM76IOx@xps> In-Reply-To: <2601191342CEEE43887BDE71AB977258A0AB30B1@irsmsx105.ger.corp.intel.com> References: <039ED4275CED7440929022BC67E7061153171181@SHSMSX103.ccr.corp.intel.com> <2601191342CEEE43887BDE71AB977258A0AB30B1@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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:59:57 -0000 22/03/2018 13:27, Ananyev, Konstantin: > Hi Qi, > > > >Hi: > > In rte_eth_dev_rx|tx_queue_start, dev_started is not checked > > > > Which mean we can call > > Rte_eth_rx_queue_setup > > Rte_eth_rx_qeueu_start > > > > And what we expected is the queue is started while device is still stopped, does this make sense? > > Should it return fail when device is not started? > > Good point, I think we should. Yes, I think there was no intent to start a queue of a stopped device.