From mboxrd@z Thu Jan 1 00:00:00 1970 From: Amine Kherbouche Subject: Re: [dpdk-dev, PATCHv5, 1/8] ethdev: add new API to retrieve RX/TX queue information Date: Wed, 14 Oct 2015 14:21:56 +0200 Message-ID: <561E48E4.5060908@6wind.com> References: <1443729293-20753-2-git-send-email-konstantin.ananyev@intel.com> <561E3EF2.1040507@6wind.com> <2601191342CEEE43887BDE71AB97725836AAF6E6@irsmsx105.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: "Ananyev, Konstantin" , "dev@dpdk.org" Return-path: Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by dpdk.org (Postfix) with ESMTP id 330558D9A for ; Wed, 14 Oct 2015 14:22:13 +0200 (CEST) Received: by wicgb1 with SMTP id gb1so228474329wic.1 for ; Wed, 14 Oct 2015 05:22:13 -0700 (PDT) In-Reply-To: <2601191342CEEE43887BDE71AB97725836AAF6E6@irsmsx105.ger.corp.intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Konstantin > Well, in general I am not opposed to add these fields to the structures. > In fact, I think it is a good thing to have. > But if we'll add them without making queue_info_get() feeling them properly - > it might create a lot of controversy. > So unless you prepared to make changes in all queue_info_get() too, > my opinion - let's leave it as it is for 2.2, and add new fields in later releases. Thanks for your answer, I'm almost done with all changes in queue_info_get(), so i have just to test and send a series of v6 for your series. Best, Amine Kherbouche