From: Thomas Monjalon <thomas@monjalon.net>
To: Michael Baum <michaelba@nvidia.com>
Cc: dev@dpdk.org, Matan Azrad <matan@nvidia.com>
Subject: Re: [PATCH] common/mlx5: fix redundant field in MR control structure
Date: Wed, 17 Nov 2021 10:42:57 +0100 [thread overview]
Message-ID: <3689260.RXIX8NE3PJ@thomas> (raw)
In-Reply-To: <20211116143635.1863313-1-michaelba@nvidia.com>
16/11/2021 15:36, michaelba@nvidia.com:
> From: Michael Baum <michaelba@nvidia.com>
>
> Inside the MR control structure there is a pointer to the common device.
> This pointer enables access to the global cache as well as hardware
> objects that may be required in case a new MR needs to be created.
>
> The purpose of adding this pointer into the MR control structure was to
> avoid its transfer as a parameter to all the functions of searching MR
> in the caches.
> However, adding it to this structure increased the Rx and Tx data-path
> structures, all the fields that followed it were slightly moved away
> which caused to a reduction in performance.
>
> This patch removes the pointer from the structure. It can be accessed
> through the "dev_gen_ptr" existing field using the "container_of"
> operator.
>
> Fixes: 334ed198ab4d ("common/mlx5: remove redundant parameter in MR search")
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
> drivers/common/mlx5/mlx5_common_mr.c | 42 +++++++++++++------------
> drivers/common/mlx5/mlx5_common_mr.h | 8 ++---
> drivers/compress/mlx5/mlx5_compress.c | 2 +-
> drivers/crypto/mlx5/mlx5_crypto.c | 2 +-
> drivers/net/mlx5/mlx5_rx.h | 13 ++------
> drivers/net/mlx5/mlx5_rxq.c | 3 +-
> drivers/net/mlx5/mlx5_txq.c | 3 +-
> drivers/regex/mlx5/mlx5_regex_control.c | 3 +-
> 8 files changed, 36 insertions(+), 40 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2021-11-17 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 14:36 michaelba
2021-11-17 9:42 ` Thomas Monjalon [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=3689260.RXIX8NE3PJ@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@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).