From: Raslan Darawsheh <rasland@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: allow meta modifications in legacy mode
Date: Sun, 31 Oct 2021 12:33:38 +0000 [thread overview]
Message-ID: <DM4PR12MB53126ADB3F1FB278727F9458CF899@DM4PR12MB5312.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211026151013.1349796-1-akozyrev@nvidia.com>
Hi,
> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Tuesday, October 26, 2021 6:10 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Subject: [PATCH] net/mlx5: allow meta modifications in legacy mode
>
> The MODIFY_FIELD RTE action rejects copy to/from metadata in case of the
> legacy mode extensive flow metadata support.
> It is not consistent with SET_META action that has no such restriction
> imposed. Registers A or B are used for META in legacy mode. Allow meta
> modifications in legacy mode as well.
>
> On other hand, SET_META rejects actions in case register C is not available
> even though it is not needed in legacy mode.
> Skip this check for legacy mode and allow setting META.
>
> Fixes: edf325d421 ("net/mlx5: check extended metadata for meta
> modification")
> Cc: stable@dpdk.org
>
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2021-10-31 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 15:10 Alexander Kozyrev
2021-10-26 21:21 ` [dpdk-stable] [PATCH v2] " Alexander Kozyrev
2021-10-27 3:52 ` Alexander Kozyrev
2021-10-31 12:33 ` 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=DM4PR12MB53126ADB3F1FB278727F9458CF899@DM4PR12MB5312.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@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).