From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Raslan Darawsheh <rasland@nvidia.com>,
Alexander Kozyrev <akozyrev@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix default CQE compression config
Date: Thu, 4 Feb 2021 17:29:20 +0000 [thread overview]
Message-ID: <7ab89ac0-8fd9-e416-afb2-d98be4eaf80d@intel.com> (raw)
In-Reply-To: <DM6PR12MB2748E533FDDDEF6DB3F761A4CFB39@DM6PR12MB2748.namprd12.prod.outlook.com>
On 2/4/2021 4:50 PM, Raslan Darawsheh wrote:
> Hi,
>
>> -----Original Message-----
>> From: Alexander Kozyrev <akozyrev@nvidia.com>
>> Sent: Thursday, February 4, 2021 6:07 PM
>> To: dev@dpdk.org
>> Cc: Raslan Darawsheh <rasland@nvidia.com>; ferruh.yigit@intel.com; Slava
>> Ovsiienko <viacheslavo@nvidia.com>
>> Subject: [PATCH] net/mlx5: fix default CQE compression config
>>
>> CQE compression must be enabled by default unless the rxq_cqe_comp_en
>> devarg is set to 0 or FW cannot support CQE compression for some reason.
>> The latest commit that introduced checks for FW capabilities for new
>> CQE zipping formats disables the CQE compression unless the devarg is 1.
>> Revert this logic and enable CQE compression by default again.
>> Please squash this fix with the original commit.
>>
>> Fixes: f5ae0d46b9 ("net/mlx5: check FW miniCQE format capabilities")
>>
>> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
>> ---
>
> Patch applied to next-net-mlx,
>
> Ferruh,
> Can you kindly squash it into next-net since I see you already pulled the original patch that it fixes
>
sure,
Squashed into relevant commit in next-net, thanks.
prev parent reply other threads:[~2021-02-04 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 16:07 Alexander Kozyrev
2021-02-04 16:11 ` Slava Ovsiienko
2021-02-04 16:50 ` Raslan Darawsheh
2021-02-04 17:29 ` Ferruh Yigit [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=7ab89ac0-8fd9-e416-afb2-d98be4eaf80d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=rasland@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).