Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-rdma@vger.kernel.org, Pavel Shamis <Pavel.Shamis@arm.com>
Subject: Re: [PATCH] IB/mlx5: Call io_stop_wc() after writing to WC MMIO
Date: Tue, 16 Aug 2022 15:11:40 +0300	[thread overview]
Message-ID: <YvuJfLpcKCvhRw3S@unreal> (raw)
In-Reply-To: <0-v1-c5dade92f363+11-mlx5_io_stop_wc_jgg@nvidia.com>

On Fri, Jul 29, 2022 at 01:33:38PM -0300, Jason Gunthorpe wrote:
> This new function is defined only on ARM and serves to guarantee a barrier
> in the WC operation. The barrier means that another run of this loop will
> not combine with the stores this loop created.
> 
> On x86 this is happening implicitly because of the spin_unlock().
> 
> Suggested-by: "Pavel Shamis" <Pavel.Shamis@arm.com>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
>  drivers/infiniband/hw/mlx5/mem.c | 1 +
>  1 file changed, 1 insertion(+)
> 

Thanks, applied.

      reply	other threads:[~2022-08-16 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 16:33 [PATCH] IB/mlx5: Call io_stop_wc() after writing to WC MMIO Jason Gunthorpe
2022-08-16 12:11 ` Leon Romanovsky [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=YvuJfLpcKCvhRw3S@unreal \
    --to=leon@kernel.org \
    --cc=Pavel.Shamis@arm.com \
    --cc=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    /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