From: Leon Romanovsky <leon@kernel.org>
To: Konstantin Taranov <kotaranov@linux.microsoft.com>
Cc: kotaranov@microsoft.com, pabeni@redhat.com,
haiyangz@microsoft.com, kys@microsoft.com, edumazet@google.com,
kuba@kernel.org, davem@davemloft.net, decui@microsoft.com,
wei.liu@kernel.org, longli@microsoft.com, jgg@ziepe.ca,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH rdma-next 1/3] RDMA/mana_ib: Access remote atomic for MRs
Date: Wed, 9 Apr 2025 15:28:52 +0300 [thread overview]
Message-ID: <20250409122852.GL199604@unreal> (raw)
In-Reply-To: <1743777955-2316-2-git-send-email-kotaranov@linux.microsoft.com>
On Fri, Apr 04, 2025 at 07:45:53AM -0700, Konstantin Taranov wrote:
> From: Konstantin Taranov <kotaranov@microsoft.com>
>
> Add IB_ACCESS_REMOTE_ATOMIC to the valid flags for MRs and use
> the corresponding flag bit during MR creation in the HW.
>
> Signed-off-by: Konstantin Taranov <kotaranov@microsoft.com>
> ---
> drivers/infiniband/hw/mana/mr.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/infiniband/hw/mana/mr.c b/drivers/infiniband/hw/mana/mr.c
> index f99557e..e4a9f53 100644
> --- a/drivers/infiniband/hw/mana/mr.c
> +++ b/drivers/infiniband/hw/mana/mr.c
> @@ -5,8 +5,8 @@
>
> #include "mana_ib.h"
>
> -#define VALID_MR_FLAGS \
> - (IB_ACCESS_LOCAL_WRITE | IB_ACCESS_REMOTE_WRITE | IB_ACCESS_REMOTE_READ)
> +#define VALID_MR_FLAGS (IB_ACCESS_LOCAL_WRITE | IB_ACCESS_REMOTE_WRITE | IB_ACCESS_REMOTE_READ |\
> + IB_ACCESS_REMOTE_ATOMIC)
>
> #define VALID_DMA_MR_FLAGS (IB_ACCESS_LOCAL_WRITE)
>
> @@ -24,6 +24,9 @@ mana_ib_verbs_to_gdma_access_flags(int access_flags)
> if (access_flags & IB_ACCESS_REMOTE_READ)
> flags |= GDMA_ACCESS_FLAG_REMOTE_READ;
>
> + if (access_flags & IB_ACCESS_REMOTE_ATOMIC)
> + flags |= GDMA_ACCESS_FLAG_REMOTE_ATOMIC;
Can you enable this flag unconditionally without relation to running RW?
Thanks
> +
> return flags;
> }
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-04-09 12:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 14:45 [PATCH rdma-next 0/3] RDMA/mana_ib: extend MR support Konstantin Taranov
2025-04-04 14:45 ` [PATCH rdma-next 1/3] RDMA/mana_ib: Access remote atomic for MRs Konstantin Taranov
2025-04-09 12:28 ` Leon Romanovsky [this message]
2025-04-10 13:37 ` [EXTERNAL] " Konstantin Taranov
2025-04-10 13:54 ` Leon Romanovsky
2025-04-14 9:15 ` Konstantin Taranov
2025-04-04 14:45 ` [PATCH rdma-next 2/3] RDMA/mana_ib: support of the zero based MRs Konstantin Taranov
2025-04-04 14:45 ` [PATCH rdma-next 3/3] RDMA/mana_ib: Add support of 4M, 1G, and 2G pages Konstantin Taranov
2025-04-09 12:27 ` Leon Romanovsky
2025-04-10 13:38 ` [EXTERNAL] " Konstantin Taranov
2025-04-10 13:55 ` Leon Romanovsky
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=20250409122852.GL199604@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=jgg@ziepe.ca \
--cc=kotaranov@linux.microsoft.com \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wei.liu@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;
as well as URLs for NNTP newsgroup(s).