From: Thomas Monjalon <thomas@monjalon.net>
To: ferruh.yigit@intel.com, bruce.richardson@intel.com,
konstantin.ananyev@intel.com
Cc: stable@dpdk.org, keith.wiles@intel.com,
Yongseok Koh <yskoh@mellanox.com>,
dev@dpdk.org, Shahaf Shuler <shahafs@mellanox.com>,
anatoly.burakov@intel.com, justin.parus@microsoft.com,
christian.ehrhardt@canonical.com, david.coronel@canonical.com,
josh.powers@canonical.com, jay.vosburgh@canonical.com,
dan.streetman@canonical.com
Subject: Re: [dpdk-stable] AVX512 bug on SkyLake
Date: Sat, 10 Nov 2018 03:13:29 +0100 [thread overview]
Message-ID: <15598804.PupyfcORSR@xps> (raw)
In-Reply-To: <1612642.At0RDolh7h@xps>
Below is my conclusion for this bug.
An expert of x86 is required to follow-up.
Summary:
- CPU: Intel Skylake
- Linux environment: Ubuntu 18.04
- Compiler: GCC 7 or 8
- Scenario: testpmd crashes when it starts forwarding
- Behaviour: AVX2 version of rte_memcpy() fails if optimized for AVX512
- Context: inline rte_memcpy() is called from
inline rte_mempool_put_bulk(), called from
mlx5_tx_complete() (inline or not)
- Analysis: AVX512 optimization changes vmovdqu to vmovdqu8
Latest status can be found in Bugzilla:
https://bugs.dpdk.org/show_bug.cgi?id=97#c35
next prev parent reply other threads:[~2018-11-10 2:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 21:23 [dpdk-stable] [PATCH] build: disable compiler AVX512F support Yongseok Koh
2018-11-01 23:11 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2018-11-02 12:42 ` [dpdk-stable] " Ferruh Yigit
2018-11-02 13:48 ` Ferruh Yigit
2018-11-02 20:59 ` Yongseok Koh
2018-11-02 21:46 ` Ferruh Yigit
2018-11-02 23:31 ` Yongseok Koh
2018-11-02 21:04 ` [dpdk-stable] [PATCH v2] " Yongseok Koh
2018-11-05 14:06 ` [dpdk-stable] [dpdk-dev] " Wiles, Keith
2018-11-06 21:30 ` Yongseok Koh
2018-11-07 9:04 ` Wiles, Keith
2018-11-08 15:59 ` [dpdk-stable] AVX512 bug on SkyLake Thomas Monjalon
2018-11-08 17:21 ` Ferruh Yigit
2018-11-08 23:01 ` Yongseok Koh
2018-11-09 6:27 ` Christian Ehrhardt
2018-11-09 9:49 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit
2018-11-09 11:35 ` Thomas Monjalon
2018-11-09 10:03 ` [dpdk-stable] " Ferruh Yigit
2018-11-09 13:17 ` Thomas Monjalon
2018-11-09 14:27 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2018-11-09 20:06 ` Ferruh Yigit
2018-11-09 18:46 ` Stephen Hemminger
2018-11-10 2:13 ` Thomas Monjalon [this message]
2018-11-11 14:15 ` [dpdk-stable] " Ananyev, Konstantin
2018-11-11 18:15 ` Thomas Monjalon
2018-11-12 9:09 ` Christian Ehrhardt
2018-11-12 9:21 ` Thomas Monjalon
2018-11-12 9:26 ` Ananyev, Konstantin
2018-11-03 1:06 ` [dpdk-stable] [PATCH v3] build: disable gcc AVX512F support Yongseok Koh
2018-11-04 20:56 ` [dpdk-stable] [dpdk-dev] " 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=15598804.PupyfcORSR@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dan.streetman@canonical.com \
--cc=david.coronel@canonical.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jay.vosburgh@canonical.com \
--cc=josh.powers@canonical.com \
--cc=justin.parus@microsoft.com \
--cc=keith.wiles@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.com \
/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).