From: Tariq Toukan <ttoukan.linux@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH V2 net-next] net/mlx4_en: avoid one cache line miss to ring doorbell
Date: Sun, 3 Oct 2021 11:05:54 +0300 [thread overview]
Message-ID: <c677b3d3-62d4-7e1c-24a0-a099ce28f12a@gmail.com> (raw)
In-Reply-To: <20211001005249.3945672-1-eric.dumazet@gmail.com>
On 10/1/2021 3:52 AM, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> This patch caches doorbell address directly in struct mlx4_en_tx_ring.
>
> This removes the need to bring in cpu caches whole struct mlx4_uar
> in fast path.
>
> Note that mlx4_uar is not guaranteed to be on a local node,
> because mlx4_bf_alloc() uses a single free list (priv->bf_list)
> regardless of its node parameter.
>
> This kind of change does matter in presence of light/moderate traffic.
> In high stress, this read-only line would be kept hot in caches.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Tariq Toukan <tariqt@nvidia.com>
> ---
> V2: added __iomem attribute to remove sparse errors (Jakub)
>
> drivers/net/ethernet/mellanox/mlx4/en_tx.c | 4 ++--
> drivers/net/ethernet/mellanox/mlx4/mlx4_en.h | 1 +
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
Thanks for your patch.
Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
prev parent reply other threads:[~2021-10-03 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 0:52 [PATCH V2 net-next] net/mlx4_en: avoid one cache line miss to ring doorbell Eric Dumazet
2021-10-03 8:05 ` Tariq Toukan [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=c677b3d3-62d4-7e1c-24a0-a099ce28f12a@gmail.com \
--to=ttoukan.linux@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tariqt@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).