From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>,
Ali Alnubani <alialnu@nvidia.com>, Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"stable@dpdk.org" <stable@dpdk.org>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: RE: [PATCH] net/mlx5: fix risk in Rx descriptor read in NEON vector path
Date: Tue, 7 Mar 2023 16:59:01 +0000 [thread overview]
Message-ID: <DM6PR12MB3753B9E4A5108168DF80A9FADFB79@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <AS8PR08MB708010B02ACC5528662B404E9E579@AS8PR08MB7080.eurprd08.prod.outlook.com>
> -----Original Message-----
> From: Ruifeng Wang <Ruifeng.Wang@arm.com>
> Sent: четверг, 29 сентября 2022 г. 09:51
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Ali Alnubani
> <alialnu@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Cc: dev@dpdk.org; Honnappa Nagarahalli
> <Honnappa.Nagarahalli@arm.com>; stable@dpdk.org; nd <nd@arm.com>; nd
> <nd@arm.com>
> Subject: RE: [PATCH] net/mlx5: fix risk in Rx descriptor read in NEON vector
> path
> Hi Slava,
>
> Are there any further comments?
>
Hi, Ruifeng
I've recalled the context and re-reviewed the patch.
There is no performance impact and I'm run out of objections 😊
My sincere apologizes for the long delay ☹
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2023-03-07 16:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 3:00 Ruifeng Wang
2022-02-10 6:24 ` Ruifeng Wang
2022-02-10 8:16 ` Slava Ovsiienko
2022-02-10 8:29 ` Ruifeng Wang
2022-05-19 14:56 ` Ali Alnubani
2022-06-20 5:37 ` Slava Ovsiienko
2022-06-27 11:08 ` Ruifeng Wang
2022-06-29 7:55 ` Slava Ovsiienko
2022-06-29 11:41 ` Ruifeng Wang
2022-09-29 6:51 ` Ruifeng Wang
2023-03-07 16:59 ` Slava Ovsiienko [this message]
2023-05-30 5:48 ` [PATCH v2] " Ruifeng Wang
2023-06-19 12:13 ` Raslan Darawsheh
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=DM6PR12MB3753B9E4A5108168DF80A9FADFB79@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=alialnu@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=nd@arm.com \
--cc=stable@dpdk.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).