From: Bruce Richardson <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "Kavanagh,
Mark B" <mark.b.kavanagh-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: Minimum Supported x86 microarchitecture
Date: Wed, 15 Apr 2015 17:05:27 +0100 [thread overview]
Message-ID: <20150415160527.GA9836@bricha3-MOBL3> (raw)
In-Reply-To: <DC5AD7FA266D86499789B1BCAEC715F846DA64E3-pww93C2UFcwu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Wed, Apr 15, 2015 at 03:09:39PM +0000, Kavanagh, Mark B wrote:
> Hi,
>
> The recent reimplementation of rte_memcpy in DPDK v2.0.0 seems to have a placed an implicit floor on the microarchitecture/Instruction set supported by DPDK.
>
> For example, I can't compile head of OVS against DPDK 2.0 with gcc without passing the 'msse3' flag; this points to an implicit minimum supported CPU of 'core2'. More discussion on same is available here: http://openvswitch.org/pipermail/dev/2015-April/053523.html
>
> Can anyone confirm or deny this, and is/should it be documented?
>
> Thanks in advance,
> Mark
SSE3 is the minimum necessary. However, I believe all x86_64 cpus have at least
SSE3 support, so this should only be a problem with 32-bit builds. Is this the
case for you?
/Bruce
next prev parent reply other threads:[~2015-04-15 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 15:09 Minimum Supported x86 microarchitecture Kavanagh, Mark B
[not found] ` <DC5AD7FA266D86499789B1BCAEC715F846DA64E3-pww93C2UFcwu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-04-15 16:05 ` Bruce Richardson [this message]
2015-04-15 16:09 ` Kavanagh, Mark B
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=20150415160527.GA9836@bricha3-MOBL3 \
--to=bruce.richardson-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=mark.b.kavanagh-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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).