From: Raslan Darawsheh <rasland@nvidia.com>
To: Asaf Penso <asafp@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH v2] doc: add steps to configure VF interface as trusted
Date: Mon, 7 Mar 2022 10:42:21 +0000 [thread overview]
Message-ID: <BYAPR12MB3078E32A3C65DE0D9872AC5CCF089@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220228073947.3009246-1-asafp@nvidia.com>
Hi,
> -----Original Message-----
> From: Asaf Penso <asafp@nvidia.com>
> Sent: Monday, February 28, 2022 9:40 AM
> To: dev@dpdk.org
> Cc: NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>;
> Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v2] doc: add steps to configure VF interface as trusted
>
> Trusted VF is needed to offload rules with rte_flow to a group that is bigger
> than 0.
> The configuration is done in two parts: driver and FW.
>
> This patch adds the needed steps to configure a VF to be trusted.
>
> Signed-off-by: Asaf Penso <asafp@nvidia.com>
> Reviewed-by: Raslan Darawsheh <rasland@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-03-07 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 15:46 [PATCH 1/1] doc: add steps to configure VF interface as trusted Asaf Penso
2022-02-27 16:44 ` Stephen Hemminger
2022-02-27 17:24 ` Thomas Monjalon
2022-02-27 18:24 ` Stephen Hemminger
2022-02-28 8:13 ` Asaf Penso
2022-02-28 7:39 ` [PATCH v2] " Asaf Penso
2022-02-28 8:09 ` Asaf Penso
2022-02-28 8:11 ` [PATCH v3] " Asaf Penso
2022-03-07 12:10 ` Raslan Darawsheh
2022-03-07 10:42 ` 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=BYAPR12MB3078E32A3C65DE0D9872AC5CCF089@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=thomas@monjalon.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.