From: Kevin Traynor <ktraynor@redhat.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, stable@dpdk.org
Cc: Alexander Kozyrev <akozyrev@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>,
Matan Azrad <matan@mellanox.com>
Subject: Re: [dpdk-stable] [PATCH 18.11] net/mlx5: fix vectorized Rx burst termination
Date: Thu, 3 Sep 2020 10:36:48 +0100 [thread overview]
Message-ID: <900f997c-da79-e6b1-b352-8986e889bfe3@redhat.com> (raw)
In-Reply-To: <20200902225148.17532-1-akozyrev@nvidia.com>
On 02/09/2020 23:51, Alexander Kozyrev wrote:
> From: Alexander Kozyrev <akozyrev@mellanox.com>
>
> [ upstream commit c9cc554ba423641d3515671269c5648dab3bb9ad ]
>
> Maximum burst size of Vectorized Rx burst routine is set to
> MLX5_VPMD_RX_MAX_BURST(64). This limits the performance of any
> application that would like to gather more than 64 packets from
> the single Rx burst for batch processing (i.e. VPP).
>
> The situation gets worse with a mix of zipped and unzipped CQEs.
> They are processed separately and the Rx burst function returns
> small number of packets every call.
>
> Repeat the cycle of gathering packets from the vectorized Rx routine
> until a requested number of packets are collected or there are no
> more CQEs left to process.
>
> Fixes: 6cb559d67b83 ("net/mlx5: add vectorized Rx/Tx burst for x86")
> Cc: stable@dpdk.org
>
> Signed-off-by: Alexander Kozyrev <akozyrev@mellanox.com>
> Acked-by: Slava Ovsiienko <viacheslavo@mellanox.com>
> Acked-by: Matan Azrad <matan@mellanox.com>
> ---
Applied, thanks.
prev parent reply other threads:[~2020-09-03 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 22:51 Alexander Kozyrev
2020-09-03 9:36 ` Kevin Traynor [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=900f997c-da79-e6b1-b352-8986e889bfe3@redhat.com \
--to=ktraynor@redhat.com \
--cc=akozyrev@mellanox.com \
--cc=akozyrev@nvidia.com \
--cc=matan@mellanox.com \
--cc=stable@dpdk.org \
--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).