From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx.bisdn.de (mx.bisdn.de [185.27.182.31]) by dpdk.org (Postfix) with ESMTP id 5523E5A82 for ; Fri, 16 Jan 2015 15:51:57 +0100 (CET) Received: from [172.16.250.156] (unknown [172.16.250.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.bisdn.de (Postfix) with ESMTPSA id CE050A0F2F for ; Fri, 16 Jan 2015 15:51:56 +0100 (CET) Message-ID: <54B9258B.9060208@bisdn.de> Date: Fri, 16 Jan 2015 15:51:55 +0100 From: Marc Sune User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.3.0 MIME-Version: 1.0 To: dev@dpdk.org References: <20150114122352.63ef79eb@urahara> <1717148.0lUn7GOqmp@xps13> <20150115130616.GA22455@hmsreliant.think-freely.org> <12253538.YOLaLVcskf@xps13> <20150115185112.GC22455@hmsreliant.think-freely.org> In-Reply-To: <20150115185112.GC22455@hmsreliant.think-freely.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] Why nothing since 1.8.0? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 14:51:57 -0000 On 15/01/15 19:51, Neil Horman wrote: > On Thu, Jan 15, 2015 at 06:25:33PM +0100, Thomas Monjalon wrote: >> 2015-01-15 08:06, Neil Horman: >>> On Thu, Jan 15, 2015 at 10:51:38AM +0100, Thomas Monjalon wrote: >>>> 2015-01-15 04:27, Ouyang, Changchun: >>>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhang, Helin >>>>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Neil Horman >>>>>>> On Wed, Jan 14, 2015 at 12:23:52PM -0800, Stephen Hemminger wrote: >>>>>>>> Ok, so 1.8.0 came out almost a month ago and none of the patches >>>>>>>> that were deferred waiting for the release got merged since then. >>>>>>>> Last commit in git is the 1.8.0 release. >>>>>>>> >>>>>>>> Where is the post-merge window bundle, where are the later commits? >>>>>>>> Lots of patches are sitting rotting in patchwork... >>>>>>> +1, I've had the same questions. >>>>>>> Neil >>>>>> +1, Some patch set might be ready for being merged. >>>>> +1, the earlier some patches are merged into mainline, and the easier those >>>>> sequent patch sets can resolve their conflicts. >>>> +1, there are some patches which are properly reviewed >>>> >>>> Reminder: sub-tree to manage specific part of DPDK can be open on request >>> Ok, I think what you're saying here is you're too busy to handle all the patches >>> comming in at the moment. As such I'd like to propose a sub-tree encompassing >>> all the pmds in DPDK. I would envision that including all the acutal pmd's in >>> the tree, as well as the infrastructure that is used to interface them to the >>> core (i.e. the ethdev/rte_ether library). I'll gladly maintain the patch pool >>> and send you pull requests. >> [snip] >> And that doesn't account for the ~500 patches that come in via pull >> request from the wireless subtree. Nor does it account for the merge >> window for net-next being 2 months instead of dpdk's 6 months. Neil, I don't want to hinder the discussion but: could you please point me out where this wireless subtree is? Maybe I am too blind, but I cannot see it here: http://dpdk.org/browse/ We are interested in acceleration for wireless NICs. Marc [snip]