From: Luke Gorrie <luke@snabb.co>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Beyond DPDK 2.0
Date: Fri, 8 May 2015 12:02:48 +0200 [thread overview]
Message-ID: <CAA2XHbdyqtL+y1N3gJixf8Hyu2UpkLS_y72xwn6yV9U=Vke-1A@mail.gmail.com> (raw)
In-Reply-To: <20150508094233.GC7376@bricha3-MOBL3>
On 8 May 2015 at 11:42, Bruce Richardson <bruce.richardson@intel.com> wrote:
> The code in those directories is "common" code that is maintained by Intel
> -
> which is why you see repeated comments about not modifying it for DPDK. It
> is
> just contained in it's own subfolder in each DPDK driver for easier
> updating
> off the internal Intel baseline.
>
Thanks for pointing this out to me, Bruce. Food for thought.
Cheers,
-Luke
next prev parent reply other threads:[~2015-05-08 10:02 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 10:38 O'Driscoll, Tim
2015-04-22 15:11 ` O'Driscoll, Tim
2015-04-22 15:33 ` Stephen Hemminger
2015-04-23 11:36 ` O'Driscoll, Tim
2015-04-24 21:02 ` Dave Neary
2015-05-07 14:02 ` Avi Kivity
2015-05-07 14:34 ` Ivan Boule
2015-05-07 15:27 ` Wiles, Keith
2015-05-07 15:33 ` Avi Kivity
2015-05-07 15:33 ` Avi Kivity
2015-05-07 15:49 ` Wiles, Keith
2015-05-07 16:05 ` Avi Kivity
2015-05-08 4:16 ` Wiles, Keith
2015-05-08 5:29 ` Luke Gorrie
2015-05-08 9:06 ` Bruce Richardson
2015-05-08 9:32 ` Luke Gorrie
2015-05-08 9:42 ` Bruce Richardson
2015-05-08 10:02 ` Luke Gorrie [this message]
2015-05-08 14:44 ` Wiles, Keith
2015-05-08 16:16 ` Stephen Hemminger
2015-05-08 10:26 ` Hobywan Kenoby
2015-05-08 13:31 ` Neil Horman
2015-05-08 16:22 ` Stephen Hemminger
2015-05-07 15:34 ` Luke Gorrie
2015-05-08 4:31 ` Wiles, Keith
2015-04-24 7:47 ` Luke Gorrie
2015-04-24 15:29 ` O'Driscoll, Tim
2015-04-24 17:00 ` Neil Horman
2015-04-26 9:07 ` Luke Gorrie
2015-04-24 17:39 ` Jay Rolette
2015-04-24 17:51 ` Matthew Hall
2015-04-25 13:30 ` Marc Sune
2015-04-25 16:08 ` Wiles, Keith
2015-04-26 21:56 ` Neil Horman
2015-04-27 2:29 ` Jim Thompson
2015-04-27 13:07 ` Neil Horman
2015-04-27 16:07 ` Stephen Hemminger
2015-04-28 7:20 ` Dor Laor
[not found] ` <D162FA4E.1DED8%keith.wiles@intel.com>
2015-04-27 9:52 ` Marc Sune
2015-04-27 13:39 ` Wiles, Keith
2015-04-27 15:34 ` Marc Sune
2015-04-27 10:29 ` Neil Horman
2015-04-27 13:50 ` Wiles, Keith
2015-04-27 15:23 ` Neil Horman
2015-04-27 12:38 ` Dave Neary
2015-04-27 13:41 ` Neil Horman
2015-04-27 16:09 ` Stephen Hemminger
2015-04-24 18:12 ` Matt Laswell
2015-04-24 18:51 ` Neil Horman
2015-04-24 19:55 ` Jay Rolette
2015-04-25 12:10 ` Neil Horman
2015-04-27 13:46 ` Jay Rolette
2015-04-28 17:26 ` Neil Horman
2015-04-28 20:02 ` Jay Rolette
2015-04-28 6:22 ` Matthew Hall
2015-04-28 17:48 ` Stephen Hemminger
2015-04-30 21:31 Wiles, Keith
2015-04-30 21:38 ` 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='CAA2XHbdyqtL+y1N3gJixf8Hyu2UpkLS_y72xwn6yV9U=Vke-1A@mail.gmail.com' \
--to=luke@snabb.co \
--cc=bruce.richardson@intel.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).