DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas F Herbert <thomasfherbert@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>,
	Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	therbert@redhat.com, Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: [dpdk-dev] GitHub sandbox for the DPDK community
Date: Sat, 02 May 2015 08:37:59 -0400	[thread overview]
Message-ID: <5544C527.6050109@gmail.com> (raw)
In-Reply-To: <20150502114059.GB28845@hmsreliant.think-freely.org>

On 5/2/15 7:40 AM, Neil Horman wrote:
> On Fri, May 01, 2015 at 01:36:58PM -0700, Matthew Hall wrote:
>> On Fri, May 01, 2015 at 10:59:32PM +0300, Aaro Koskinen wrote:
>>> Projects like GCC, GLIBC, binutils, busybox, etc or what?
>>>
>>> A.
>> You'll notice all of these are low-level UNIX hacker sorts of tools mostly,
>> with the partial exception of busybox. But even that is mainly for embedded
>> use. It doesn't mean I don't think they're good and useful, but it does limit
>> the possible size of the community in my view.
>>
>> Since we are talking about how to get the largest widest community possible
>> for DPDK, it could require doing things a bit differently from how many
>> low-level tools have historically done things.
A look at gmane, http://dir.gmane.org/gmane.comp.networking.dpdk.devel, 
confirms the explosion of interest in DPDK in the last 6 months with 
postings up to almost 70/day.  There is no problem with lack of interest 
in DPDK nor is there a need to change the mechanics of hosting the 
source to widen the audience. The case for DPDK is really compelling, 
the idea for reducing the HW complexity by accelerating switch functions 
on commodity HW is a fantastic benefit. Easily integrated accelerated 
programmable switch functions is a great advantage as well.

I do think there may be an argument for increasing the number of 
reviewers/maintainers or subdivide according to ares of interest perhaps 
into 4 categories:
1. PMD drivers
2. librte core
3. applications
4. vhost

--TFH

>>
> Why?
>
> Contributors to GCC: ~600 (based on svn) review
> Contrubutors to glibc : ~300 (based on git) review
> Contributors to binutils: ~600
> Contributors to busybox: ~300
>
> Contributors to DPDK: ~125
>
> Now I grant you that dpdk is a newer, much more niche project, but its
> disingenuous to state that we _have_ to do things differently to reach a wider
> audience.  We can, but its by no means a prerequisite to gainining a wider
> audience.
>


-- 
Thomas F. Herbert

  reply	other threads:[~2015-05-02 12:38 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 15:56 Wiles, Keith
2015-05-01 16:45 ` Neil Horman
2015-05-01 17:18   ` Aaro Koskinen
2015-05-04 12:39     ` Qiu, Michael
2015-05-01 17:31   ` Matthew Hall
2015-05-01 17:45     ` Wiles, Keith
2015-05-01 18:48     ` Neil Horman
2015-05-01 19:10       ` Wiles, Keith
2015-05-02  2:59         ` Wiles, Keith
2015-05-03 21:00         ` Neil Horman
2015-05-04  3:51           ` Wiles, Keith
2015-05-04 12:43     ` Qiu, Michael
2015-05-04 17:48       ` Matthew Hall
2015-05-04 18:52         ` Neil Horman
2015-05-05  3:12         ` Wiles, Keith
2015-05-05  3:25           ` Jim Thompson
2015-05-05 13:55             ` Neil Horman
2015-05-05 16:43               ` Wiles, Keith
2015-05-05 17:57                 ` John W. Linville
2015-05-05 18:30                   ` Wiles, Keith
2015-05-05 18:46                     ` John W. Linville
2015-05-05 19:07                 ` Neil Horman
2015-05-05 20:15                   ` Wiles, Keith
2015-05-06  8:12                 ` Panu Matilainen
2015-05-06  8:30                   ` Simon Kågström
2015-05-06  9:00                     ` Panu Matilainen
2015-05-06 10:37                     ` Neil Horman
2015-05-07 15:26                   ` John W. Linville
2015-05-01 18:01   ` Wiles, Keith
2015-05-01 18:09 ` Stephen Hemminger
2015-05-01 18:17   ` Wiles, Keith
2015-05-04 20:34     ` Marc Sune
2015-05-05  2:54       ` Wiles, Keith
2015-05-01 19:49   ` Matthew Hall
2015-05-01 19:59     ` Aaro Koskinen
2015-05-01 20:36       ` Matthew Hall
2015-05-02 11:40         ` Neil Horman
2015-05-02 12:37           ` Thomas F Herbert [this message]
2015-05-02 14:07             ` Wiles, Keith
2015-05-02 13:59           ` Wiles, Keith
2015-05-04 21:08             ` Marc Sune
2015-05-05  3:09               ` Wiles, Keith
2015-05-04  6:52 ` Simon
2015-05-04  9:05   ` Marc Sune
2015-05-06 10:11 ` Mcnamara, John
2015-05-06 21:09 ` Thomas Monjalon
2015-05-06 21:37   ` Marc Sune
2015-05-06 23:49     ` Wiles, Keith
2015-05-07  3:37       ` Wiles, Keith
2015-05-12 14:38         ` Thomas Monjalon
2015-05-04  5:08 Wiles, Keith

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=5544C527.6050109@gmail.com \
    --to=thomasfherbert@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=dev@dpdk.org \
    --cc=mhall@mhcomputing.net \
    --cc=nhorman@tuxdriver.com \
    --cc=therbert@redhat.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).