From: Thomas Monjalon <thomas@monjalon.net>
To: Bing Zhao <bingz@mellanox.com>
Cc: john.mcnamara@intel.com, marko.kovacevic@intel.com,
viacheslavo@mellanox.com, orika@mellanox.com, matan@mellanox.com,
shahafs@mellanox.com, rasland@mellanox.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] doc: update hairpin data buffer size config
Date: Wed, 22 Apr 2020 04:13:22 +0200 [thread overview]
Message-ID: <2215228.yKrmzQ4Hd0@thomas> (raw)
In-Reply-To: <1587454163-127981-1-git-send-email-bingz@mellanox.com>
21/04/2020 09:29, Bing Zhao:
> This patch updates the MLX5 PMD and release notes documentations.
> Adding the guideline for hairpin data buffer size configuration.
>
> Signed-off-by: Bing Zhao <bingz@mellanox.com>
> Acked-by: Ori Kam <orika@mellanox.com>
> ---
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> +- ``hp_buf_log_sz`` parameter [int]
> +
> + The total data buffer size of a hairpin queue (logarithmic form), in bytes.
> + PMD will set the data buffer size to 2 ** ``hp_buf_log_sz``, both for RX & TX.
> + The capacity of the value is sepcified by the Firmware, and the initialization
sepcified -> specified
Firmware -> firmware
> + will get a failure if it is out of scope.
> + The range of the value is from 11 to 19 right now, and the supported frame
> + size of a single packet for hairpin is from 512B to 128KB. It might change if
> + different Firmware release is being used. By using a small value, it could
Firmware -> firmware
> + reduce the memory consumption but not work with large frame. If the value is
> + too large, the memory consumption will be high and some potential performance
> + degradation will be introduced.
> + By default PMD will set this value to 16, which mean that 9KB jumbo frames
By default, the PMD
> + will be supported.
> +
> --- a/doc/guides/rel_notes/release_20_05.rst
> +++ b/doc/guides/rel_notes/release_20_05.rst
> @@ -62,6 +62,7 @@ New Features
>
> * Added support for matching on IPv4 Time To Live and IPv6 Hop Limit.
> * Added support for creating Relaxed Ordering Memory Regions.
> + * Added support for configuring Haripin queue data buffer size.
Haripin -> Hairpin
next prev parent reply other threads:[~2020-04-22 2:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 15:50 [dpdk-dev] [PATCH] " Bing Zhao
2020-04-20 9:57 ` Ori Kam
2020-04-21 5:32 ` [dpdk-dev] [PATCH v2] " Bing Zhao
2020-04-21 6:38 ` Ori Kam
2020-04-21 7:29 ` [dpdk-dev] [PATCH v3] " Bing Zhao
2020-04-22 2:13 ` Thomas Monjalon [this message]
2020-04-22 3:14 ` Bing Zhao
2020-04-22 3:11 ` [dpdk-dev] [PATCH v4] " Bing Zhao
2020-05-05 8:55 ` Raslan Darawsheh
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=2215228.yKrmzQ4Hd0@thomas \
--to=thomas@monjalon.net \
--cc=bingz@mellanox.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=matan@mellanox.com \
--cc=orika@mellanox.com \
--cc=rasland@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=viacheslavo@mellanox.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).