From: Raslan Darawsheh <rasland@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>, Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix CQE decompression for ARM and PowerPC
Date: Mon, 2 Nov 2020 14:57:11 +0000 [thread overview]
Message-ID: <DM6PR12MB274844452BE5C11B195EFD4BCF100@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201029175822.1615-1-akozyrev@nvidia.com>
Hi,
> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Thursday, October 29, 2020 7:58 PM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Subject: [PATCH] net/mlx5: fix CQE decompression for ARM and PowerPC
Fixed styling issue ARM->Arm
>
> The recent Rx code refactoring moved the incrementing
> of the CQ completion index out of the rxq_cq_decompress_v()
> function to the rxq_burst_v() function.
>
> The advancing of CQ completion index was removed in SSE
> version only causing Neon and Altivec Rx bursts to stall.
>
> Remove the incrementation of CQ completion index for all
> the architectures in order to fix the stall.
>
> Fixes: bf7d5157ed ("net/mlx5: refactor vectorized Rx")
Fixed commit id
>
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> ---
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-11-02 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 17:58 Alexander Kozyrev
2020-11-01 16:39 ` Slava Ovsiienko
2020-11-02 14:57 ` Raslan Darawsheh [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=DM6PR12MB274844452BE5C11B195EFD4BCF100@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=viacheslavo@nvidia.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).