From: Jerin Jacob <jerinjacobk@gmail.com>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: Jerin Jacob <jerinj@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
dpdk-dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: fix octeontx2 eventdev devargs
Date: Fri, 21 Feb 2020 15:43:32 +0530 [thread overview]
Message-ID: <CALBAE1Oj-CO2gJfnLGDPkMc_sHR1LsBdHnDjCQ7TdDvSSn2qQg@mail.gmail.com> (raw)
In-Reply-To: <20200219065511.3877-1-pbhagavatula@marvell.com>
On Wed, Feb 19, 2020 at 12:25 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Fix OCTEON TX2 event device devargs examples.
>
> Fixes: 55e778ca4648 ("event/octeontx2: add devargs for inflight buffer count")
> Cc: stable@dpdk.org
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Reviewed-by: Jerin Jacob <jerinj@marvell.com>
Thomas,
This is the only patch for RC4 from the eventdev tree.
Could you please merge this directly to dpdk.git?
> ---
> doc/guides/eventdevs/octeontx2.rst | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/doc/guides/eventdevs/octeontx2.rst b/doc/guides/eventdevs/octeontx2.rst
> index fad84cf42..d4b2515ce 100644
> --- a/doc/guides/eventdevs/octeontx2.rst
> +++ b/doc/guides/eventdevs/octeontx2.rst
> @@ -66,7 +66,7 @@ Runtime Config Options
> upper limit for in-flight events.
> For example::
>
> - --dev "0002:0e:00.0,xae_cnt=16384"
> + -w 0002:0e:00.0,xae_cnt=16384
>
> - ``Force legacy mode``
>
> @@ -74,7 +74,7 @@ Runtime Config Options
> single workslot mode in SSO and disable the default dual workslot mode.
> For example::
>
> - --dev "0002:0e:00.0,single_ws=1"
> + -w 0002:0e:00.0,single_ws=1
>
> - ``Event Group QoS support``
>
> @@ -89,7 +89,7 @@ Runtime Config Options
> default.
> For example::
>
> - --dev "0002:0e:00.0,qos=[1-50-50-50]"
> + -w 0002:0e:00.0,qos=[1-50-50-50]
>
> - ``Selftest``
>
> @@ -98,7 +98,7 @@ Runtime Config Options
> The tests are run once the vdev creation is successfully complete.
> For example::
>
> - --dev "0002:0e:00.0,selftest=1"
> + -w 0002:0e:00.0,selftest=1
>
> - ``TIM disable NPA``
>
> @@ -107,7 +107,7 @@ Runtime Config Options
> parameter disables NPA and uses software mempool to manage chunks
> For example::
>
> - --dev "0002:0e:00.0,tim_disable_npa=1"
> + -w 0002:0e:00.0,tim_disable_npa=1
>
> - ``TIM modify chunk slots``
>
> @@ -118,7 +118,7 @@ Runtime Config Options
> to SSO. The default value is 255 and the max value is 4095.
> For example::
>
> - --dev "0002:0e:00.0,tim_chnk_slots=1023"
> + -w 0002:0e:00.0,tim_chnk_slots=1023
>
> - ``TIM enable arm/cancel statistics``
>
> @@ -126,7 +126,7 @@ Runtime Config Options
> event timer adapter.
> For example::
>
> - --dev "0002:0e:00.0,tim_stats_ena=1"
> + -w 0002:0e:00.0,tim_stats_ena=1
>
> - ``TIM limit max rings reserved``
>
> @@ -136,7 +136,7 @@ Runtime Config Options
> rings.
> For example::
>
> - --dev "0002:0e:00.0,tim_rings_lmt=5"
> + -w 0002:0e:00.0,tim_rings_lmt=5
>
> - ``TIM ring control internal parameters``
>
> @@ -146,7 +146,7 @@ Runtime Config Options
> default values.
> For Example::
>
> - --dev "0002:0e:00.0,tim_ring_ctl=[2-1023-1-0]"
> + -w 0002:0e:00.0,tim_ring_ctl=[2-1023-1-0]
>
> Debugging Options
> ~~~~~~~~~~~~~~~~~
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-02-21 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 6:55 pbhagavatula
2020-02-21 10:13 ` Jerin Jacob [this message]
2020-02-21 10:16 ` Thomas Monjalon
2020-02-21 17:16 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
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=CALBAE1Oj-CO2gJfnLGDPkMc_sHR1LsBdHnDjCQ7TdDvSSn2qQg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=pbhagavatula@marvell.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).