From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: yong.liu@intel.com, xiaolong.ye@intel.com,
ferruh.yigit@intel.com, dev@dpdk.org
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-dev] [PATCH] net/virtio: fix AVX512 datapath selection
Date: Mon, 11 May 2020 16:47:20 +0200 [thread overview]
Message-ID: <20200511144720.241224-1-maxime.coquelin@redhat.com> (raw)
The AVX512 packed ring datapath selection was only done
at build time, but it should also be checked at runtime
that the CPU supports it.
This patch add a CPU flags check so that non-vectorized
path is selected at runtime if AVX512 is not supported.
Fixes: ccb10995c2ad ("net/virtio: add election for vectorized path")
Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
---
drivers/net/virtio/virtio_ethdev.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/net/virtio/virtio_ethdev.c b/drivers/net/virtio/virtio_ethdev.c
index 312871cb48..49ccef12c7 100644
--- a/drivers/net/virtio/virtio_ethdev.c
+++ b/drivers/net/virtio/virtio_ethdev.c
@@ -1965,8 +1965,10 @@ eth_virtio_dev_init(struct rte_eth_dev *eth_dev)
PMD_DRV_LOG(INFO,
"building environment do not support packed ring vectorized");
#else
- hw->use_vec_rx = 1;
- hw->use_vec_tx = 1;
+ if (rte_cpu_get_flag_enabled(RTE_CPUFLAG_AVX512F)) {
+ hw->use_vec_rx = 1;
+ hw->use_vec_tx = 1;
+ }
#endif
}
}
--
2.25.4
next reply other threads:[~2020-05-11 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 14:47 Maxime Coquelin [this message]
2020-05-11 15:11 ` Ferruh Yigit
2020-05-11 18:48 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2020-05-11 19:49 ` Maxime Coquelin
2020-05-11 22:21 ` Ferruh Yigit
2020-05-12 3:29 ` Liu, Yong
2020-05-12 8:36 ` Maxime Coquelin
2020-05-12 8:46 ` Liu, Yong
2020-05-12 10:04 ` Maxime Coquelin
2020-05-12 13:19 ` Liu, Yong
2020-05-12 2:27 ` [dpdk-dev] [PATCH] " Liu, Yong
2020-05-12 8:35 ` Maxime Coquelin
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=20200511144720.241224-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=xiaolong.ye@intel.com \
--cc=yong.liu@intel.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).