From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Cc: daniel chapiesky <dchapiesky2@gmail.com>
Subject: Re: [dpdk-dev] to the intel dpdk engineers and all contributors
Date: Wed, 15 Oct 2014 15:11:01 -0700 [thread overview]
Message-ID: <20141015221101.GA26568@mhcomputing.net> (raw)
In-Reply-To: <CAJnwcoPrq-=cO7vWC5CnqYf9-8ObM2ECLb3RqhvV6-96go-EiQ@mail.gmail.com>
On Wed, Oct 15, 2014 at 04:46:41PM -0400, daniel chapiesky wrote:
> At time 4:30, he mentioned the "shock to the system" of developers
> expecting a pat on the back and instead receiving critiques of their
> code.....
>
> I realized that I was one of those who failed to acknowledge the incredible
> work the Intel Engineers and other contributors have produced.
To be clear, the only way you know if your open source is popular is if
everybody finds the bugs and tries to work around and/or patch and/or file
them to keep improving the product! Open source is only good when it does have
bugs and critiques and if it doesn't it's probably unused or buggy. :-D
That being said, DPDK is a TON easier to work with than trying to do
bare-metal or use a bunch of complicated expensive custom packet processing
hardware. It's trying to solve a very complex problem, and the code is much
cleaner than most similar networking code I've ever used.
So nobody working on it should take any of the stuff people might say
personally... they wouldn't say it if they weren't beating on the product and
using it to do other complex tasks of their own.
Matthew.
next prev parent reply other threads:[~2014-10-15 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 20:46 daniel chapiesky
2014-10-15 21:28 ` O'driscoll, Tim
2014-10-15 22:11 ` Matthew Hall [this message]
2014-10-16 1:34 ` Wiles, Roger 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=20141015221101.GA26568@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dchapiesky2@gmail.com \
--cc=dev@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).