DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marc Sune <marc.sune@bisdn.de>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Why nothing since 1.8.0?
Date: Fri, 16 Jan 2015 15:51:55 +0100	[thread overview]
Message-ID: <54B9258B.9060208@bisdn.de> (raw)
In-Reply-To: <20150115185112.GC22455@hmsreliant.think-freely.org>


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]

  parent reply	other threads:[~2015-01-16 14:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 20:23 Stephen Hemminger
2015-01-14 21:01 ` Neil Horman
2015-01-15  4:15   ` Zhang, Helin
2015-01-15  4:27     ` Ouyang, Changchun
2015-01-15  9:51       ` Thomas Monjalon
2015-01-15 13:06         ` Neil Horman
2015-01-15 17:25           ` Thomas Monjalon
2015-01-15 18:51             ` Neil Horman
2015-01-15 21:55               ` O'driscoll, Tim
2015-01-16  1:46                 ` Matthew Hall
2015-01-16  7:16                   ` Thomas Monjalon
2015-01-16 16:51                 ` Neil Horman
2015-01-17 19:57                   ` O'driscoll, Tim
2015-01-18  0:30                     ` Stephen Hemminger
     [not found]                     ` <20150118182508.GA21891@hmsreliant.think-freely.org>
2015-01-18 21:48                       ` O'driscoll, Tim
2015-01-19 13:30                         ` Neil Horman
2015-01-15 22:23               ` Thomas Monjalon
2015-01-16 17:20                 ` Neil Horman
2015-01-16 18:18                   ` Thomas Monjalon
2015-01-16 18:58                     ` Matthew Hall
2015-01-16 20:00                       ` Neil Horman
2015-01-16 20:38                         ` Matthew Hall
2015-01-16 21:14                           ` Neil Horman
2015-01-16 22:43                             ` Matthew Hall
2015-01-16 19:53                     ` Neil Horman
2015-01-16 14:51               ` Marc Sune [this message]
2015-01-16 16:56                 ` Neil Horman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54B9258B.9060208@bisdn.de \
    --to=marc.sune@bisdn.de \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).