DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Why nothing since 1.8.0?
Date: Thu, 15 Jan 2015 18:25:33 +0100	[thread overview]
Message-ID: <12253538.YOLaLVcskf@xps13> (raw)
In-Reply-To: <20150115130616.GA22455@hmsreliant.think-freely.org>

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.

The list of PMDs is increasing:
	librte_pmd_af_packet
	librte_pmd_bond
	librte_pmd_e1000
	librte_pmd_enic
	librte_pmd_i40e
	librte_pmd_ixgbe
	librte_pmd_pcap
	librte_pmd_ring
	librte_pmd_virtio
	librte_pmd_vmxnet3
	librte_pmd_xenvirt
There is already some sub-trees for bnx2x, fm10k and i40e:
	http://dpdk.org/browse/

> If you could set me up with a login to dpdk.org, I'd appreciate it.

It is preferred to have 1 sub-tree per module.
What do you think of managing contributions for af_packet and/or virtio?
It would make sense as virtio is a RedHat technology.
Maybe it could include vhost lib and example.

Thanks for proposing
-- 
Thomas

  reply	other threads:[~2015-01-15 17:25 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 [this message]
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
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=12253538.YOLaLVcskf@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.com \
    /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).