DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Roger Keith" <keith.wiles@windriver.com>
To: daniel chapiesky <dchapiesky2@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] to the intel dpdk engineers and all contributors
Date: Thu, 16 Oct 2014 01:34:53 +0000	[thread overview]
Message-ID: <27316A25-99E8-4D95-9070-CA58B9B4D1A1@windriver.com> (raw)
In-Reply-To: <CAJnwcoPrq-=cO7vWC5CnqYf9-8ObM2ECLb3RqhvV6-96go-EiQ@mail.gmail.com>


On Oct 15, 2014, at 1:46 PM, daniel chapiesky <dchapiesky2@gmail.com> wrote:

> I just watched the closing remarks by Tim Driscol at the dpdk summit....
> 
> http://youtu.be/r-JA5NBybrs
> 
> 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.
> 
> Please let me acknowledge all of you and your efforts with a few comments:
> 
> 1) Kudos!!:
> 
> 2) The Packet Framework made me run around waving my hands in the air
> yelling: "This is freaking awesome! I don't have to write it myself!!!"
> 
> 3) The layered architecture is elegant.
> 
> 4) Examples???? The examples are wonderful! Those who wrote the examples
> are my heroes.
> 
> 5) Docs? Clear, to the point, and better than the other projects we depend
> upon (you know who you are)
> 
> 6) 6Wind - Thank you for taking on the management of the repository and
> website - your coordination effort is truly appreciated
> 
> 7) Did I say the Packet Framework saved me so much time I was actually able
> to cut back my coffee intake by 10%!!!!
> 
> 8) Windriver - PktGen!!!!!  (though I really want to know more about
> mcos….)

If you need more information about MCOS let me know as I did not write a lot of docs for it :-(

Thanks
++Keith
> 
> Finally,
> 
> I recently received a pat on the back for the application I have developed.
> In truth, that pat should be passed on, since my application depends so
> heavily on DPDK.
> 
> Thank you.
> 
> I encourage others to let the Intel Engineers and contributors know how
> much we appreciate the time and effort they have given to DPDK.
> 
> Sincerely,
> 
> 
> Daniel Chapiesky
> AllSource

Keith Wiles, Principal Technologist with CTO office, Wind River mobile 972-213-5533

      parent reply	other threads:[~2014-10-16  1:27 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
2014-10-16  1:34 ` Wiles, Roger Keith [this message]

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=27316A25-99E8-4D95-9070-CA58B9B4D1A1@windriver.com \
    --to=keith.wiles@windriver.com \
    --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).