DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@6wind.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 3/3] config: rename "default" machine type as "core2"
Date: Mon, 19 May 2014 10:20:08 +0200	[thread overview]
Message-ID: <CALwxeUuwrBvPGkYGc70zE_WUM1fd1tQES62i70Xe4=hC0xiEnQ@mail.gmail.com> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B01AA19C02@IRSMSX103.ger.corp.intel.com>

Bruce,


On Wed, May 14, 2014 at 5:18 PM, Richardson, Bruce <
bruce.richardson@intel.com> wrote:

>
> This patch I'm not so sure about. For 64-bit, the term "default" is pretty
> much correct, as it should work for any 64-bit IA cpu AFAIK, since all
> 64-bit cpus should have the necessary SSE instructions to run DPDK. For
> 32-bit it's perhaps not so clear cut, but I think the baseline being
> "default" rather than a specific uarch is good to keep.
>


Ok.
I was not too fond of "core2" either.
If "default" must be understood as "works fine on all platform", it is
quite sound this way.

Let's just drop this patch.

Thanks.

-- 
David Marchand

      reply	other threads:[~2014-05-19  8:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 14:58 [dpdk-dev] [PATCH 0/3] configs cleanup David Marchand
2014-05-14 14:58 ` [dpdk-dev] [PATCH 1/3] config: factorize configurations David Marchand
2014-05-14 15:10   ` Richardson, Bruce
2014-05-19  8:13     ` David Marchand
2014-05-21 14:33     ` Thomas Monjalon
2014-05-14 14:58 ` [dpdk-dev] [PATCH 2/3] config: rename "default" configuration file as "native" David Marchand
2014-05-14 15:12   ` Richardson, Bruce
2014-05-21 14:35     ` Thomas Monjalon
2014-05-14 14:58 ` [dpdk-dev] [PATCH 3/3] config: rename "default" machine type as "core2" David Marchand
2014-05-14 15:18   ` Richardson, Bruce
2014-05-19  8:20     ` David Marchand [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='CALwxeUuwrBvPGkYGc70zE_WUM1fd1tQES62i70Xe4=hC0xiEnQ@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).