From: Alexander Kozyrev <akozyrev@nvidia.com>
To: dev@dpdk.org
Cc: rasland@nvidia.com, ferruh.yigit@intel.com, viacheslavo@nvidia.com
Subject: [dpdk-dev] [PATCH] net/mlx5: fix default CQE compression config
Date: Thu, 4 Feb 2021 16:07:28 +0000 [thread overview]
Message-ID: <20210204160728.16048-1-akozyrev@nvidia.com> (raw)
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>
---
drivers/net/mlx5/linux/mlx5_os.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/mlx5/linux/mlx5_os.c b/drivers/net/mlx5/linux/mlx5_os.c
index 79a4376f91..2dc079779d 100644
--- a/drivers/net/mlx5/linux/mlx5_os.c
+++ b/drivers/net/mlx5/linux/mlx5_os.c
@@ -867,6 +867,8 @@ mlx5_dev_spawn(struct rte_device *dpdk_dev,
mprq_caps.max_single_wqe_log_num_of_strides;
}
#endif
+ /* Rx CQE compression is enabled by default. */
+ config->cqe_comp = 1;
#ifdef HAVE_IBV_DEVICE_TUNNEL_SUPPORT
if (dv_attr.comp_mask & MLX5DV_CONTEXT_MASK_TUNNEL_OFFLOADS) {
tunnel_en = ((dv_attr.tunnel_offloads_caps &
--
2.24.1
next reply other threads:[~2021-02-04 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 16:07 Alexander Kozyrev [this message]
2021-02-04 16:11 ` Slava Ovsiienko
2021-02-04 16:50 ` Raslan Darawsheh
2021-02-04 17:29 ` Ferruh Yigit
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=20210204160728.16048-1-akozyrev@nvidia.com \
--to=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).