public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: ynachum@amazon.com
Cc: leon@kernel.org, linux-rdma@vger.kernel.org, sleybo@amazon.com,
	matua@amazon.com, mrgolin@amazon.com,
	Firas Jahjah <firasj@amazon.com>
Subject: Re: [PATCH] RDMA/efa: Add rdma write capability to device caps
Date: Fri, 21 Apr 2023 19:20:42 -0300	[thread overview]
Message-ID: <ZEMMOl+xJ1NOq9Np@nvidia.com> (raw)
In-Reply-To: <20230404154313.35194-1-ynachum@amazon.com>

On Tue, Apr 04, 2023 at 03:43:13PM +0000, ynachum@amazon.com wrote:
> From: Yonatan Nachum <ynachum@amazon.com>
> 
> Add rdma write capability that is propagated from the device to
> rdma-core.
> Enable MR creation with remote write permissions according to this
> device capability.
> 
> Reviewed-by: Firas Jahjah <firasj@amazon.com>
> Reviewed-by: Michael Margolin <mrgolin@amazon.com>
> Signed-off-by: Yonatan Nachum <ynachum@amazon.com>
> ---
>  .../infiniband/hw/efa/efa_admin_cmds_defs.h   | 12 ++++--
>  drivers/infiniband/hw/efa/efa_io_defs.h       | 42 +++++++++++++------
>  drivers/infiniband/hw/efa/efa_verbs.c         |  6 ++-
>  include/uapi/rdma/efa-abi.h                   |  1 +
>  4 files changed, 44 insertions(+), 17 deletions(-)

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2023-04-21 22:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 15:43 [PATCH] RDMA/efa: Add rdma write capability to device caps ynachum
2023-04-09  7:32 ` Leon Romanovsky
2023-04-09 11:28   ` Nachum, Yonatan
2023-04-09 17:21     ` Leon Romanovsky
2023-04-10 12:24       ` Nachum, Yonatan
2023-04-10 12:38         ` Leon Romanovsky
2023-04-10 14:14           ` Nachum, Yonatan
2023-04-13  8:22             ` Leon Romanovsky
2023-04-13 13:43               ` Nachum, Yonatan
2023-04-18 14:03                 ` Nachum, Yonatan
2023-04-21 22:20 ` Jason Gunthorpe [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=ZEMMOl+xJ1NOq9Np@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=firasj@amazon.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=matua@amazon.com \
    --cc=mrgolin@amazon.com \
    --cc=sleybo@amazon.com \
    --cc=ynachum@amazon.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