From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by dpdk.org (Postfix) with ESMTP id 1F85B108D for ; Thu, 26 Jan 2017 19:02:08 +0100 (CET) Received: by mail-wm0-f41.google.com with SMTP id c206so97814930wme.0 for ; Thu, 26 Jan 2017 10:02:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=ihG0ItxUbQeM0nbLmhlYckIE3dQFEaqYhJUWBVk3ERU=; b=Tti7PQvOIFHNvWgxr0b9qaFwMqQtzWTFPbyy5KeARoagntcT7DstG5xzxMv82SwNAY S28IvoTEmi6LChgubrtHDkEn3UZeFs/42Glf+I1Ky9ZadLxRq58lJK15YRzgBk8Xt8C9 jMO31xZMRgOTA1h/NWIq3zUfsU/24Yek+H8INSAEQuumhN90Yc80pu9+GIsNU1NICXWf AMMmN6uFNOBXlRQ6FaXf8vIFvFLLlpUAb+P1O0oDk4q1/vAzfGZVVlqjUEWyjljP9faH 8olANTvDNFzZ7asEp/NwZZVs0VeVFkKJTNsZdSdlxwrcd0NGZsDGgj5pH04paojE6PnW HoHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=ihG0ItxUbQeM0nbLmhlYckIE3dQFEaqYhJUWBVk3ERU=; b=KJH8LnYdkPG5Cr3TcVJqCHjxyDR2XWimuAokAK7vlGdN5hjYQIKP5YG0KawPyGhrwm 5IDeYXzEeJbikpULLItN0/YyoiDSu5wnHyOow+VUZHOUg6tS0OUOBae7wwNe7AtyONaI XSOYA1apTU2K9VMP8nwxEdy2yzptC73qLMM5L7Y0Ea9tl5wgjA3E5fmYaVeQvqTUO02k Xs7x6wRSeuM06TAvcehIcre9ylqauaBOHXZWjdUGlHNw/CGsds0iUaoTvjk49W5Rc9bW xQBh+asYOzFhftwzEUQJ+NMhkJwlln2cfbkbiDPCK2RBIKRCZvkmvpB+Jy4bvV2409s/ /GjA== X-Gm-Message-State: AIkVDXJAxjn4LqNlgZ8csCzslT3p06VLVCDvgpGXFrC1PG1vx1K6Y7CBSSCpz//jHQB2+KqG X-Received: by 10.28.63.5 with SMTP id m5mr3991685wma.95.1485453727792; Thu, 26 Jan 2017 10:02:07 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id 36sm3740642wrz.8.2017.01.26.10.02.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Jan 2017 10:02:07 -0800 (PST) From: Thomas Monjalon To: Hemant Agrawal , Ferruh Yigit Cc: dev@dpdk.org, bruce.richardson@intel.com, shreyansh.jain@nxp.com, john.mcnamara@intel.com, jerin.jacob@caviumnetworks.com Date: Thu, 26 Jan 2017 19:02:06 +0100 Message-ID: <3259922.9T20GZHyr3@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <99c7a139-6098-b7ce-25a1-ee3efb045ff0@nxp.com> References: <1484832240-2048-1-git-send-email-hemant.agrawal@nxp.com> <67f91414-0439-952d-e07f-23556db110d9@intel.com> <99c7a139-6098-b7ce-25a1-ee3efb045ff0@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCHv6 00/33] NXP DPAA2 PMD 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, 26 Jan 2017 18:02:08 -0000 2017-01-26 17:48, Hemant Agrawal: > On 1/26/2017 5:25 PM, Ferruh Yigit wrote: > > On 1/23/2017 5:56 PM, Ferruh Yigit wrote: > >> I have some concerns about this PMD, > >> > >> - This is a big one, as seen above, and it is hard to review it all, I > >> don't feel confident about the amount of review done, more reviewers are > >> welcome. And we are already post RC1. > >> > >> - Although this driver introduces a new bus type, in some parts, driver > >> still has virtual devices like usage, perhaps this is not because of > >> this PMD but mostly because of overall dpdk bus structure. Still I have > >> concerns about getting driver like this, and would like to hear more > >> comments. > > > > As a result of above concerns, I propose postponing this PMD to 17.05 > > release. > > > > The dependent rte_bus just get into main repo less than two weeks ago, > > also this driver comes with a few new things first of its kind, and it > > matters to make first samples correct. > > > > I believe it is good to let the PMD be around a little more to give > > chance to both PMD and rte_bus to become more mature. > > > > I agree that this driver is coming with few new thing and it is taking > time to come up with agreeable and good solution for some of this new stuff. > > Finalizing the right framework for adding SoC based drivers took a > little longer than expected. But thanks to Thomas help in the last that > we got the basic bus framework integrated. > > Thomos- is it possible to integrate it early in 17.05 cycle, rather than > waiting till end? Yes that's a really good question. I could reword it to "when do we pull from next-* trees"? I think you and Ferruh can work to integrate it in next-net before the beginning of 17.05. So I could do a first pull of next-net when starting the 17.05 cycle. Note that 17.05 will start in few weeks.