From: Matthew Hall <mhall@mhcomputing.net>
To: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Why nothing since 1.8.0?
Date: Thu, 15 Jan 2015 17:46:26 -0800 [thread overview]
Message-ID: <20150116014626.GA14696@mhcomputing.net> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C9978E@IRSMSX102.ger.corp.intel.com>
On Thu, Jan 15, 2015 at 09:55:00PM +0000, O'driscoll, Tim wrote:
> As you said, there's a balance to be struck, and too many subtrees may
> become unmanageable. With respect to your concern about developers having to
> potentially develop patches against multiple subtrees, this has never been
> raised as a concern by any of our development team. Is there any historical
> data on the number of changes that would fall into this category so we can
> see if it's a real problem or not?
Hi Tim,
What happens when a core API like rte_mbuf gets some changes, and you have to
update the PMD's to fit?
Do I have to make 10-20 odd random patches to separate PMD maintainers instead
of one set of patches to the PMD subtree?
To me it doesn't sound very nice for the guys maintaining the core. Given most
of the changes seem to be mbuf or eal this seems like a scaling issue to me.
But maybe I misunderstood the process.
Matthew.
next prev parent reply other threads:[~2015-01-16 1:48 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 [this message]
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=20150116014626.GA14696@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=tim.o'driscoll@intel.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).