DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rahul Bhansali <rbhansali@marvell.com>
Cc: dev@dpdk.org, Nithin Dabilpuram <ndabilpuram@marvell.com>,
	 Kiran Kumar K <kirankumark@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	 Satha Rao <skoteshwar@marvell.com>,
	Harman Kalra <hkalra@marvell.com>,
	jerinj@marvell.com
Subject: Re: [PATCH 7/7] doc: updates cnxk doc for new devargs
Date: Thu, 29 May 2025 23:28:34 +0530	[thread overview]
Message-ID: <CALBAE1NEH_drPodG0UDFJkXQavR4QcM4vdxqYrZrCama4mk=WQ@mail.gmail.com> (raw)
In-Reply-To: <20250528115122.24052-7-rbhansali@marvell.com>

On Wed, May 28, 2025 at 5:32 PM Rahul Bhansali <rbhansali@marvell.com> wrote:
>
> Adds details of below nix devargs
> - force_tail_drop
> - disable_xqe_drop
>
> Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>


Squashed this patch to relevant commit and Series Applied to
dpdk-next-net-mrvl/for-main. Thanks



> ---
>  doc/guides/nics/cnxk.rst | 23 +++++++++++++++++++++++
>  1 file changed, 23 insertions(+)
>
> diff --git a/doc/guides/nics/cnxk.rst b/doc/guides/nics/cnxk.rst
> index 35f95dcc0a..7f4ff7b4fb 100644
> --- a/doc/guides/nics/cnxk.rst
> +++ b/doc/guides/nics/cnxk.rst
> @@ -470,6 +470,29 @@ Runtime Config Options
>     With the above configuration, inline inbound IPsec post-processing
>     should be done by the application.
>
> +- ``Enable force tail drop feature`` (default ``0``)
> +
> +   Force tail drop can be enabled by specifying ``force_tail_drop`` ``devargs``
> +   parameter.
> +   This option is for OCTEON CN10K SoC family.
> +
> +   For example::
> +
> +      -a 0002:02:00.0,force_tail_drop=1
> +
> +   With the above configuration, descriptors are internally increased and back
> +   pressures are optimized to avoid CQ full situation due to inflight packets.
> +
> +- ``Disable RQ XQE drop`` (default ``0``)
> +
> +   Rx XQE drop can be disabled by specifying ``disable_xqe_drop`` ``devargs``
> +   parameter.
> +   This option is for OCTEON CN10K SoC family.
> +
> +   For example::
> +
> +      -a 0002:02:00.0,disable_xqe_drop=1
> +
>  .. note::
>
>     Above devarg parameters are configurable per device, user needs to pass the
> --
> 2.25.1
>

      reply	other threads:[~2025-05-29 17:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 11:51 [PATCH 1/7] common/cnxk: fix CQ tail drop feature Rahul Bhansali
2025-05-28 11:51 ` [PATCH 2/7] common/cnxk: set CQ drop and backpressure threshold Rahul Bhansali
2025-05-28 11:51 ` [PATCH 3/7] net/cnxk: devarg to set force tail drop Rahul Bhansali
2025-05-28 11:51 ` [PATCH 4/7] net/cnxk: fix descriptor count update on reconfig Rahul Bhansali
2025-05-28 11:51 ` [PATCH 5/7] common/cnxk: disable xqe drop config in RQ context Rahul Bhansali
2025-05-28 11:51 ` [PATCH 6/7] net/cnxk: devarg option to disable xqe drop Rahul Bhansali
2025-05-28 11:51 ` [PATCH 7/7] doc: updates cnxk doc for new devargs Rahul Bhansali
2025-05-29 17:58   ` Jerin Jacob [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='CALBAE1NEH_drPodG0UDFJkXQavR4QcM4vdxqYrZrCama4mk=WQ@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=rbhansali@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).