From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Asaf Penso <asafp@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Matan Azrad <matan@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add information for Rx burst functions in mlx5
Date: Mon, 23 Nov 2020 07:17:17 +0000 [thread overview]
Message-ID: <MWHPR12MB1501E6AD07E196C1DEED4DA5DFFC0@MWHPR12MB1501.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1606048553-16127-1-git-send-email-asafp@nvidia.com>
Hi, Asaf
There is one more devargs to manage MPRQ enable: "rxqs_min_mprq".
This parameters defines the number of Rx queues limit to enable MPRQ.
If there is not enough Rx queues (below the limit) then MPRQ is disabled.
By default, "rxqs_min_mprq" is 12. I suppose we should mention this in
the list being added.
With best regards, Slava
> -----Original Message-----
> From: Asaf Penso <asafp@nvidia.com>
> Sent: Sunday, November 22, 2020 14:36
> To: dev@dpdk.org
> Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>; Raslan
> Darawsheh <rasland@nvidia.com>
> Subject: [PATCH] doc: add information for Rx burst functions in mlx5
>
> mlx5 pmd supports various rx_burst functions.
> Each function is enabled differently and supports different features.
>
> Add more comprehensive information about each function.
>
> Signed-off-by: Asaf Penso <asafp@nvidia.com>
> ---
> doc/guides/nics/mlx5.rst | 55
> ++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 55 insertions(+)
>
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index
> 205e5ba..8c1ce15 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -1645,3 +1645,58 @@ all flows with assistance of external tools.
> .. code-block:: console
>
> mlx_steering_dump.py -f <output_file>
> +
> +RX burst functions
> +------------------
> +
> +This section describes the different rx_burst functions and provides an
> +elaborated information.
> +
> +#. Function name - rx_burst
> + How to enable - rx_vec_en=0
> + Scatter support - Yes
> + RX error recovery support - Yes
> + CQE compression support - Yes
> + Large MTU support - The maximal packet size should be set to be the
> + same as the MTU size. The mbuf size can be
> + according to the application needs since the
> + pmd can perform the scatter.
> +
> +#. Function name - rx_burst_vec
> + How to enable - rx_vec_en=1 (default value)
> + Scatter support - No
> + RX error recovery support - Supported only in case CQE compression is off
> + CQE compression support - Yes
> + Large MTU support - No. Scatter is not supported, so it means
> + that the mbuf must be with the same size of
> + the MTU. In this case, maximal packet size ==
> + mbuf size == MTU size
> + Fallback - In scatter or LRO fallback to rx_burst
> + Notes - Improves CPU utilization for single-core and
> + improves performance
> +
> +#. Function name - rx_burst_mprq
> + How to enable - mprq_en=1
> + Scatter support - No
> + RX error recovery support - Yes
> + CQE compression support - Yes
> + Large MTU support - Yes. Needs to be turned on by specifying the
> + stride size
> + Notes - Saving PCI bandwidth and getting higher
> + performance, especially for small packets.
> + Used mainly for multi-core use cases.
> + Uses externally attached buffers only.
> +
> +#. Function name - rx_burst_mprq_vec
> + How to enable - rx_vec_en=1 (default mode) and mprq_en=1
> + Scatter support - No
> + RX error recovery support - Supported only in case CQE compression is off
> + CQE compression support - Yes
> + Large MTU support - Yes. Needs to be turned on by specifying the
> + stride size
> + Fallback - In scatter or LRO fallback to rx_burst_mprq
> + Notes - Improves CPU utilization of regular
> + rx_burst_mprq for multi-core and improves
> + performance.
> + Used mainly for multi-core use cases.
> + Uses externally attached buffers only.
> \ No newline at end of file
> --
> 1.8.3.1
next prev parent reply other threads:[~2020-11-23 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 12:35 Asaf Penso
2020-11-23 7:17 ` Slava Ovsiienko [this message]
2020-11-23 7:56 ` [dpdk-dev] [PATCH v2] " Asaf Penso
2020-11-23 8:04 ` [dpdk-dev] [PATCH v3] " Asaf Penso
2020-11-23 8:14 ` Slava Ovsiienko
2020-11-24 7:44 ` [dpdk-dev] [PATCH v4] " Asaf Penso
2020-11-26 23:55 ` [dpdk-dev] [PATCH v5] doc: add Rx functions limitations in mlx5 guide Thomas Monjalon
2020-11-27 0:04 ` 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=MWHPR12MB1501E6AD07E196C1DEED4DA5DFFC0@MWHPR12MB1501.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--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).