From: Harris, James R <james.r.harris at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Compiling error on different types of Intel CPU
Date: Tue, 22 May 2018 04:08:57 +0000 [thread overview]
Message-ID: <33BC82CF-DA16-4C12-AC1F-F8D829E36DAF@intel.com> (raw)
In-Reply-To: CAMxP3BQ_XawAzh=AJPLC=hBZRJndyEWcb0N=o9Yh_+N7JCKxhg@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
From: SPDK <spdk-bounces(a)lists.01.org> on behalf of Bob Chen <a175818323(a)gmail.com>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org>
Date: Monday, May 21, 2018 at 8:23 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Compiling error on different types of Intel CPU
2018-05-21 23:25 GMT+08:00 Harris, James R <james.r.harris(a)intel.com<mailto:james.r.harris(a)intel.com>>:
Hi Bob,
DPDK builds by default with –march=native. This means when the app is compiled on the E5v4 (Broadwell Xeon) it may use instructions available on the E5v4 which are not available on the E5v2 (Ivy Bridge Xeon).
Could you try “make clean” followed by “make DPDK_CFLAGS=-march=ivybridge”?
Alternatively, you can modify dpdk/config/defconfig_spdk-linuxapp-gcc – change CONFIG_RTE_MACHINE to “ivybridge”. Then “make clean” and rebuild.
I assume it could work, but I still need to prepare two packages for each type of servers.
Is there any possibility that I could build a compatible software and let it run on both of them?
And who knows what would happen when things come to the next Skylake platform...
The “ivybridge” packages would work on both the E5v2 (Ivy Bridge) and E5v4 (Haswell) systems, as well as Skylake and future microarchitectures.
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5845 bytes --]
next reply other threads:[~2018-05-22 4:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 4:08 Harris, James R [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-11 16:12 [SPDK] Compiling error on different types of Intel CPU E.W.Z.
2019-03-11 15:23 Harris, James R
2019-03-11 12:48 Ernest Zed
2018-05-22 14:00 Kulasek, TomaszX
2018-05-22 7:09 Bob Chen
2018-05-22 3:23 Bob Chen
2018-05-21 15:25 Harris, James R
2018-05-21 15:18 Verkamp, Daniel
2018-05-21 13:31 Marushak, Nathan
2018-05-21 12:21 Luse, Paul E
2018-05-21 8:11 Bob Chen
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=33BC82CF-DA16-4C12-AC1F-F8D829E36DAF@intel.com \
--to=spdk@lists.01.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