From: Raslan Darawsheh <rasland@nvidia.com>
To: Lior Margalit <lmargalit@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: Lior Margalit <lmargalit@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Alexander Kozyrev <akozyrev@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v1] net/mlx5: fix assertion on the flags set in pkt mbuf
Date: Sun, 9 Jan 2022 11:54:51 +0000 [thread overview]
Message-ID: <BYAPR12MB3078A33BC5BEF3A2542F6231CF4F9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211223081541.3095005-1-lmargalit@nvidia.com>
Hi,
> -----Original Message-----
> From: Lior Margalit <lmargalit@nvidia.com>
> Sent: Thursday, December 23, 2021 10:16 AM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>
> Cc: Lior Margalit <lmargalit@nvidia.com>; dev@dpdk.org; Alexander Kozyrev
> <akozyrev@nvidia.com>; stable@dpdk.org
> Subject: [PATCH v1] net/mlx5: fix assertion on the flags set in pkt mbuf
>
> Fixed the assertion on the flags set in pkt->ol_flags for vectorized MPRQ.
> With vectorized MPRQ the CQs are processed before copying the MPRQ bufs
> so the valid assertion is that the expected flag is set and not that the pkt-
> >ol_flags equlas this flag alone.
>
> Fixes: 0f20acbf5eda ("net/mlx5: implement vectorized MPRQ burst")
> Cc: akozyrev@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Lior Margalit <lmargalit@nvidia.com>
> Acked-by: Slava Ovsiienko <viacheslavo@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-01-09 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 8:15 Lior Margalit
2022-01-09 11:54 ` Raslan Darawsheh [this message]
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=BYAPR12MB3078A33BC5BEF3A2542F6231CF4F9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=lmargalit@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).