From: "Coyle, David" <david.coyle@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 2/3] net/ice: fix segment fault in AVX512
Date: Tue, 6 Apr 2021 12:21:51 +0000 [thread overview]
Message-ID: <MN2PR11MB355094AFE1E123B4DBE7734FE3769@MN2PR11MB3550.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1617082176-51391-3-git-send-email-wenzhuo.lu@intel.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Wenzhuo Lu
> Sent: Tuesday, March 30, 2021 6:30 AM
> To: dev@dpdk.org
> Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH v3 2/3] net/ice: fix segment fault in AVX512
>
> Fix segment fault when failing to get the memory from the pool.
>
> Fixes: 7f85d5ebcfe1 ("net/ice: add AVX512 vector path")
> Cc: stable@dpdk.org
>
> Reported-by: David Coyle <David.Coyle@intel.com>
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
> ---
> drivers/net/ice/ice_rxtx_vec_avx2.c | 120 +-------------------
> drivers/net/ice/ice_rxtx_vec_avx512.c | 5 +-
> drivers/net/ice/ice_rxtx_vec_common.h | 203
> ++++++++++++++++++++++++++++++++++
> 3 files changed, 209 insertions(+), 119 deletions(-)
>
The patch fixes the seg fault, but note I have only tested the default '#ifndef RTE_LIBRTE_ICE_16BYTE_RX_DESC' path
Tested-by: David Coyle <david.coyle@intel.com>
next prev parent reply other threads:[~2021-04-06 12:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 3:15 [dpdk-dev] [PATCH v2 0/3] fix segment fault in avx512 Wenzhuo Lu
2021-03-30 3:15 ` [dpdk-dev] [PATCH v2 1/3] net/iavf: fix segment fault in AVX512 Wenzhuo Lu
2021-03-30 3:15 ` [dpdk-dev] [PATCH v2 2/3] net/ice: " Wenzhuo Lu
2021-03-30 3:15 ` [dpdk-dev] [PATCH v2 3/3] net/i40e: " Wenzhuo Lu
2021-03-30 5:29 ` [dpdk-dev] [PATCH v3 0/3] fix segment fault in avx512 code Wenzhuo Lu
2021-03-30 5:29 ` [dpdk-dev] [PATCH v3 1/3] net/iavf: fix segment fault in AVX512 Wenzhuo Lu
2021-04-06 12:20 ` Coyle, David
2021-03-30 5:29 ` [dpdk-dev] [PATCH v3 2/3] net/ice: " Wenzhuo Lu
2021-04-06 12:21 ` Coyle, David [this message]
2021-03-30 5:29 ` [dpdk-dev] [PATCH v3 3/3] net/i40e: " Wenzhuo Lu
2021-04-06 12:22 ` Coyle, David
2021-04-08 8:36 ` [dpdk-dev] [PATCH v3 0/3] fix segment fault in avx512 code Zhang, Qi Z
2021-04-09 3:01 ` [dpdk-dev] [PATCH v4 " Wenzhuo Lu
2021-04-09 3:01 ` [dpdk-dev] [PATCH v4 1/3] net/iavf: fix segment fault in AVX512 Wenzhuo Lu
2021-04-13 12:37 ` Ferruh Yigit
2021-04-14 1:18 ` Lu, Wenzhuo
2021-04-09 3:01 ` [dpdk-dev] [PATCH v4 2/3] net/ice: " Wenzhuo Lu
2021-04-13 12:39 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2021-04-14 1:20 ` Lu, Wenzhuo
2021-04-09 3:01 ` [dpdk-dev] [PATCH v4 3/3] net/i40e: " Wenzhuo Lu
2021-04-09 7:00 ` [dpdk-dev] [PATCH v4 0/3] fix segment fault in avx512 code Zhang, Qi Z
2021-04-14 7:25 ` [dpdk-dev] [PATCH v5 " Wenzhuo Lu
2021-04-14 7:25 ` [dpdk-dev] [PATCH v5 1/3] net/iavf: fix segment fault in AVX512 Wenzhuo Lu
2021-04-14 7:25 ` [dpdk-dev] [PATCH v5 2/3] net/ice: " Wenzhuo Lu
2021-04-14 7:25 ` [dpdk-dev] [PATCH v5 3/3] net/i40e: " Wenzhuo Lu
2021-04-14 12:28 ` [dpdk-dev] [PATCH v5 0/3] fix segment fault in avx512 code Zhang, Qi Z
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=MN2PR11MB355094AFE1E123B4DBE7734FE3769@MN2PR11MB3550.namprd11.prod.outlook.com \
--to=david.coyle@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@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).