From: David Marchand <david.marchand@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] config: default to shared library
Date: Wed, 4 Mar 2015 14:57:50 +0100 [thread overview]
Message-ID: <CALwxeUtvB=sSgJfpNA6aqWO_W2sMobw1EQFwMTAk88vWrik25A@mail.gmail.com> (raw)
In-Reply-To: <20150304134911.GC544@bricha3-MOBL3>
On Wed, Mar 4, 2015 at 2:49 PM, Bruce Richardson <bruce.richardson@intel.com
> wrote:
> On Wed, Mar 04, 2015 at 03:41:49PM +0200, Panu Matilainen wrote:
> > Right, but then there's "ivshmem" that doesn't fit that description
> either
> > AFAICS.
>
> Ah, yes, forgotten about that one! :-)
Well, this is out of scope, but this config file should not exist in the
first place.
>From my point of view, the ivshmem implementation is just badly hooked into
the eal, and this is the only reason why ivshmem should have a build option
(disabled) by default.
If we could cleanup this, then there would be no exception to the naming
convention.
--
David Marchand
next prev parent reply other threads:[~2015-03-04 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 6:17 Panu Matilainen
2015-03-04 9:24 ` Thomas Monjalon
2015-03-04 10:42 ` Bruce Richardson
2015-03-04 11:05 ` Panu Matilainen
2015-03-04 11:28 ` Neil Horman
2015-03-04 13:08 ` Bruce Richardson
2015-03-04 13:24 ` Panu Matilainen
2015-03-04 13:31 ` Bruce Richardson
2015-03-04 13:41 ` Panu Matilainen
2015-03-04 13:49 ` Bruce Richardson
2015-03-04 13:56 ` Thomas Monjalon
2015-03-04 13:57 ` David Marchand [this message]
2015-03-04 14:10 ` Bruce Richardson
2015-03-04 11:29 ` Thomas Monjalon
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='CALwxeUtvB=sSgJfpNA6aqWO_W2sMobw1EQFwMTAk88vWrik25A@mail.gmail.com' \
--to=david.marchand@6wind.com \
--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).