From: Ori Kam <orika@nvidia.com>
To: thomas@monjalon.net
Cc: orika@mellanox.com, dev@dpdk.org, stable@dpdk.org
Subject: [dpdk-stable] [PATCH v2 1/5] regex/mlx5: fix memory rule alignment
Date: Thu, 7 Jan 2021 18:57:07 +0200 [thread overview]
Message-ID: <20210107165711.1782-2-orika@nvidia.com> (raw)
In-Reply-To: <20210107165711.1782-1-orika@nvidia.com>
Due to Kernel requirement the memory allocated must be aligned to 2M.
Fixes: b34d816363b5 ("regex/mlx5: support rules import")
Cc: stable@dpdk.org
Signed-off-by: Ori Kam <orika@nvidia.com>
---
drivers/regex/mlx5/mlx5_rxp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regex/mlx5/mlx5_rxp.c b/drivers/regex/mlx5/mlx5_rxp.c
index fcbc766441..bd721f0b11 100644
--- a/drivers/regex/mlx5/mlx5_rxp.c
+++ b/drivers/regex/mlx5/mlx5_rxp.c
@@ -892,7 +892,7 @@ rxp_db_setup(struct mlx5_regex_priv *priv)
/* Setup database memories for both RXP engines + reprogram memory. */
for (i = 0; i < (priv->nb_engines + MLX5_RXP_EM_COUNT); i++) {
- priv->db[i].ptr = rte_malloc("", MLX5_MAX_DB_SIZE, 0);
+ priv->db[i].ptr = rte_malloc("", MLX5_MAX_DB_SIZE, 1 << 21);
if (!priv->db[i].ptr) {
DRV_LOG(ERR, "Failed to alloc db memory!");
ret = ENODEV;
--
2.25.1
next prev parent reply other threads:[~2021-01-07 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201217085158.28367-1-orika@nvidia.com>
2020-12-17 8:51 ` [dpdk-stable] [PATCH 1/4] " Ori Kam
2020-12-17 8:51 ` [dpdk-stable] [PATCH 3/4] regex/mlx5: fix support for group id Ori Kam
[not found] ` <20210107165711.1782-1-orika@nvidia.com>
2021-01-07 16:57 ` Ori Kam [this message]
2021-01-07 16:57 ` [dpdk-stable] [PATCH v2 3/5] " Ori Kam
2021-01-07 16:57 ` [dpdk-stable] [PATCH v2 5/5] regex/mlx5: fix num of supported queues Ori Kam
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=20210107165711.1782-2-orika@nvidia.com \
--to=orika@nvidia.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).