From: Jay Rolette <rolette@infinite.io>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] next technical board meeting, 2017-04-06
Date: Thu, 30 Mar 2017 11:03:13 -0500 [thread overview]
Message-ID: <CADNuJVqSP-VRBmFyt6EgG1CwxzQnRXKkK6okaNXBoBadS0t5NA@mail.gmail.com> (raw)
In-Reply-To: <5C76150C-195D-4316-AC3B-6AE2441B254B@intel.com>
On Thu, Mar 30, 2017 at 10:51 AM, Wiles, Keith <keith.wiles@intel.com>
wrote:
<snip>
>
> My Soap box comment:
> I think we are limiting DPDK’s growth by only focusing on a few new
> PMDs and reworking the existing code. We need to look forward and grow DPDK
> as a community to get more people involved in adding more applications and
> new designs. I believe DPDK.org needs to be a bigger community and not just
> a I/O library called DPDK. We need to actively move the organization to
> include more then just a high speed I/O library. Some will focus on DPDK
> and others will focus on providing a higher level applications, libraries
> and features.
>
> Regards,
> Keith
>
Yes!
next prev parent reply other threads:[~2017-03-30 16:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 9:41 Jerin Jacob
2017-03-30 14:25 ` Wiles, Keith
2017-03-30 15:05 ` Olivier Matz
2017-03-30 15:51 ` Wiles, Keith
2017-03-30 16:03 ` Jay Rolette [this message]
2017-03-30 18:09 ` Dumitrescu, Cristian
2017-04-03 19:51 ` Stephen Hemminger
2017-04-03 22:53 ` Wiles, Keith
2017-04-04 1:28 ` Stephen Hemminger
2017-04-04 5:01 ` Vincent Jardin
2017-04-04 14:35 ` Wiles, Keith
2017-03-31 8:52 ` Olivier Matz
2017-03-31 9:31 ` Dumitrescu, Cristian
2017-03-31 14:24 ` Wiles, Keith
2017-03-31 14:39 ` Wiles, Keith
2017-04-06 10:01 ` Jerin Jacob
2017-04-10 6:49 ` [dpdk-dev] next technical board meeting, 2017-04-10 Yuanhan Liu
2017-04-10 14:34 ` Wiles, Keith
2017-04-10 14:43 ` Dumitrescu, Cristian
2017-04-10 14:54 ` 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=CADNuJVqSP-VRBmFyt6EgG1CwxzQnRXKkK6okaNXBoBadS0t5NA@mail.gmail.com \
--to=rolette@infinite.io \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=keith.wiles@intel.com \
--cc=olivier.matz@6wind.com \
--cc=techboard@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).