From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 639711B390 for <dev@dpdk.org>; Fri, 13 Oct 2017 01:51:27 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A8D0521A18; Thu, 12 Oct 2017 19:51:26 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 12 Oct 2017 19:51:26 -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=Op5+zmgnpGUt2G69RUPHBYeleF +Lh8L4FmFpFSoaqZg=; b=GC9AeTjEcC1qg7VfcpAd2Rt52knad8h041s+QanOMF w/E7FrdF7zQhBK+soTHOt15TaAqMWjmqHySRWRm4LxwcMLE/If0MurU5OnX+xCrD lhvtoF2P2rWmb0KtUsHYccsalp601H9jtOcVMBRMWcDQasRkhuXiw69aoYNrfK9T 8= 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=fm1; bh=Op5+zm gnpGUt2G69RUPHBYeleF+Lh8L4FmFpFSoaqZg=; b=lWdHdoX+MV72AWaah0RGUU DQWExunIQyvZgSMURz/HHu6XpVLXFMBEZyHlbvYL8s7iFtxSakN6g74iBG9ZW9mJ Bk17tOmtG0ka3xuPdrcsoP1TJUIHD4f6ge8jcYcq2/OkM75LxozeAViyEGio39KM njTseEU+smxrJaZs/7lP2OS20mIMVuxWlPjnaemeXTdpc5SNuMBoupdhOzhSRNvH KlZwUtdOZoAvK7fZEdDZ4XejVmc//CdX9U1TLQiZSVKsWoMQ+D4cy+Qg+Pyipfuc zAF3rvgCKwK3e+vV76j0VpR55FzrbinTc2NBOYGNAxN1krr+hcm8m3Krg5Mur3yg == X-ME-Sender: <xms:_v_fWUT4jAFASbxYbJn3SrZLgmm7UsttDHNcAO7EBQg6waIfp4MYxw> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 27AE17F966; Thu, 12 Oct 2017 19:51:26 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: Ferruh Yigit <ferruh.yigit@intel.com> Cc: DPDK <dev@dpdk.org>, "Zhang, Helin" <helin.zhang@intel.com>, Olga Shern <olgas@mellanox.com>, Jerin Jacob <jerin.jacob@caviumnetworks.com>, Hemant Agrawal <hemant.agrawal@nxp.com>, Gaetan Rivet <gaetan.rivet@6wind.com>, Pascal Mazon <pascal.mazon@6wind.com>, "Zhu, Heqing" <heqing.zhu@intel.com>, John McNamara <john.mcnamara@intel.com>, Vincent JARDIN <vincent.jardin@6wind.com>, shahafs@mellanox.com Date: Fri, 13 Oct 2017 01:51:25 +0200 Message-ID: <9041864.FpAEQS7Gje@xps> In-Reply-To: <15fd757d-d540-d787-f525-2c881502970a@intel.com> References: <a6c5a18e-5898-2120-a7fb-7e28f1ae0e99@intel.com> <15fd757d-d540-d787-f525-2c881502970a@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Vendor specific sub-trees under next-net X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 12 Oct 2017 23:51:27 -0000 13/10/2017 01:31, Ferruh Yigit: > Hi Thomas, et al > > Previously it has been mentioned [1] to have vendor specific driver > trees under next-net. > > And recently Mellanox agreed to have a Mellanox tree [2]. > > Intel also agrees to have next-net-intel, and Helin will be maintaining > it, thanks to Helin for volunteering. Good news, thanks > Other vendors with multiple drivers are Cavium, 6wind and NXP. > > - Is there a name for Mellanox maintainer? > > - What do other vendors, mentioned above, thinks about creating their > own sub-tree? > > - Are the vendor sub-trees and their maintainers need to be approved by > tech-board? Yes every dpdk.org git trees must be approved by the techboard. The next meeting is tomorrow. > And what I understand from vendor specific sub-trees is, instead of > driver patches going into next-net directly, they will go into vendor > tree and next-net will pull from them. Yes we are creating a new git tree layer below next-net. > This will distribute the maintenance work among the vendors, also will > give more control to vendors on their patches. It is very good to distribute workload. In 17.11-rc1, there were more than 500 patches managed in next-net. Thanks Ferruh > Thanks, > ferruh > > > [1] > http://dpdk.org/ml/archives/dev/2017-September/075094.html > > [2] > http://dpdk.org/ml/archives/dev/2017-October/078277.html