From: Ferruh Yigit <ferruh.yigit@intel.com>
To: <psatheesh@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>
Cc: <dev@dpdk.org>, Ori Kam <orika@nvidia.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH 22.02 2/2] net/cnxk: add devargs for configuring SDP channel mask
Date: Tue, 11 Jan 2022 11:56:13 +0000 [thread overview]
Message-ID: <27efba59-e991-9f50-69f3-d4df7e2b7823@intel.com> (raw)
In-Reply-To: <20211109094204.2343402-2-psatheesh@marvell.com>
On 11/9/2021 9:42 AM, psatheesh@marvell.com wrote:
> From: Satheesh Paul <psatheesh@marvell.com>
>
> This patch adds support to configure channel mask which will
> be used by rte flow when adding flow rules on SDP interfaces.
>
Hi Satheesh,
+ Ori & Andrew.
What 'SDP' stands for?
And can this new devarg be provided with flow rule? Why it needs to be a new devarg?
Can you please give a sample of the rte flow API that will be used?
Thanks,
ferruh
> Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
> ---
> doc/guides/nics/cnxk.rst | 21 ++++++++++++++
> drivers/net/cnxk/cnxk_ethdev_devargs.c | 40 ++++++++++++++++++++++++--
> 2 files changed, 59 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/nics/cnxk.rst b/doc/guides/nics/cnxk.rst
> index 837ffc02b4..470e01b811 100644
> --- a/doc/guides/nics/cnxk.rst
> +++ b/doc/guides/nics/cnxk.rst
> @@ -276,6 +276,27 @@ Runtime Config Options
> set with this custom mask, inbound encrypted traffic from all ports with
> matching channel number pattern will be directed to the inline IPSec device.
>
> +- ``SDP device channel and mask`` (default ``none``)
> + Set channel and channel mask configuration for the SDP device. This
> + will be used when creating flow rules on the SDP device.
> +
> + By default, for rules created on the SDP device, the RTE Flow API sets the
> + channel number and mask to cover the entire SDP channel range in the channel
> + field of the MCAM entry. This behaviour can be modified using the
> + ``sdp_channel_mask`` ``devargs`` parameter.
> +
> + For example::
> +
> + -a 0002:1d:00.0,sdp_channel_mask=0x700/0xf00
> +
> + With the above configuration, RTE Flow rules API will set the channel
> + and channel mask as 0x700 and 0xF00 in the MCAM entries of the flow rules
> + created on the SDP device. This option needs to be used when more than one
> + SDP interface is in use and RTE Flow rules created need to distinguish
> + between traffic from each SDP interface. The channel and mask combination
> + specified should match all the channels(or rings) configured on the SDP
> + interface.
> +
> .. note::
>
<...>
next prev parent reply other threads:[~2022-01-11 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 9:42 [dpdk-dev] [PATCH 22.02 1/2] common/cnxk: support to set channel mask for SDP interfaces psatheesh
2021-11-09 9:42 ` [dpdk-dev] [PATCH 22.02 2/2] net/cnxk: add devargs for configuring SDP channel mask psatheesh
2022-01-11 11:56 ` Ferruh Yigit [this message]
2022-01-11 14:29 ` [EXT] " Satheesh Paul
2022-01-12 10:57 ` Ferruh Yigit
2021-12-21 10:18 ` [dpdk-dev] [PATCH 22.02 1/2] common/cnxk: support to set channel mask for SDP interfaces Jerin Jacob
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=27efba59-e991-9f50-69f3-d4df7e2b7823@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=orika@nvidia.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).