DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: users@dpdk.org, dev@dpdk.org
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	Hobywan Kenoby <hobywank@hotmail.com>
Subject: Re: [dpdk-dev] [dpdk-users] Project Governance and Linux Foundation
Date: Mon, 17 Oct 2016 14:40:45 +0200	[thread overview]
Message-ID: <56798548.UUDuXfq43Z@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA675F6F33@IRSMSX108.ger.corp.intel.com>

2016-10-17 11:52, O'Driscoll, Tim:
> From: Hobywan Kenoby
> > The current DPDK version can run on virtually all processors (Intel, IBM
> > and ARM) and leverage all NICs: is there **really** anyone questionning
> > openness of the community?
> 
> I still hear concerns on this, and based on discussions with others who
> put their names to the post below, they do too.
> I think it's a perception that we need to address.

It is simple to address this perception with fact checking.
The next releases will provide even more code for ARM and NPUs.
If someone submits some good code and is ignored, it is easy enough
to ping the mailing list and make it visible.
If someone sees any regression on his architecture, we care.
Please let's stop maintaining confusion on this topic.

DPDK *is* truly open.

  reply	other threads:[~2016-10-17 12:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10  8:33 [dpdk-dev] " O'Driscoll, Tim
2016-10-17 10:23 ` Hobywan Kenoby
2016-10-17 11:52   ` O'Driscoll, Tim
2016-10-17 12:40     ` Thomas Monjalon [this message]
2016-10-17 14:40       ` [dpdk-dev] [dpdk-users] " O'Driscoll, Tim
2016-10-18 13:22         ` Thomas Monjalon
2016-10-17 21:23     ` [dpdk-dev] " Dave Neary
2016-10-18 11:34       ` Jerin Jacob
2016-10-18 13:27         ` Thomas Monjalon
2016-10-18 16:26           ` Jerin Jacob
2016-10-19  8:04             ` O'Driscoll, Tim
2016-10-19  8:40               ` Dave Neary
2016-10-19  9:56                 ` Thomas Monjalon
2016-10-19  9:09               ` Jerin Jacob
     [not found] ` <20161018121629630001294@chinamobile.com>
2016-10-18 10:29   ` [dpdk-dev] [dpdk-users] How to printout PMD logs to console yingzhi
2016-10-18 10:58     ` Kavanagh, Mark B
2016-10-18 12:51   ` [dpdk-dev] [dpdk-users] Project Governance and Linux Foundation Thomas Monjalon
2016-10-21 14:00 ` [dpdk-dev] " Dave Neary
2016-10-21 17:20   ` Wiles, Keith
2016-10-22 19:27   ` Thomas Monjalon
2016-10-12  5:44 qin.chunhua
2016-10-12  7:43 ` Thomas Monjalon
2016-10-13  6:10   ` [dpdk-dev] [dpdk-users] " Muhammad Zain-ul-Abideen

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=56798548.UUDuXfq43Z@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=hobywank@hotmail.com \
    --cc=tim.odriscoll@intel.com \
    --cc=users@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).