linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH v2 for-next] RDMA/rxe: Fixes mr access supported list
Date: Tue, 20 Jun 2023 11:44:59 -0300	[thread overview]
Message-ID: <ZJG7a85CSnrkBlIQ@nvidia.com> (raw)
In-Reply-To: <20230613171654.19334-1-rpearsonhpe@gmail.com>

On Tue, Jun 13, 2023 at 12:16:55PM -0500, Bob Pearson wrote:
> A recent patch incorrectly did not include IB_ACCESS_RELAXED_ORDERING
> in the list of supported access flags for the rxe driver. The driver
> actually does nothing related to relaxed ordering but it causes no
> problems to include it as supported but with no effect. This change
> caused ib_send_bw and friends to not run correctly.
> 
> The correct approach is for the driver to allow any of the optional
> access flags and otherwise ignore them. This patch adds
> IB_ACCESS_OPTIONAL to the list of rxe supported flags.
> 
> Link: https://lore.kernel.org/linux-rdma/ZIifmHzwnvn3YVbI@nvidia.com/raw
> Fixes: 02ed253770fb ("RDMA/rxe: Introduce rxe access supported flags")
> Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
> ---
> v2: Changed the target to for-next since the error is not currently in
>     for-rc. Replaced IB_ACCESS_RELAXED_ORDERING by IB_ACCESS_OPTIONAL
>     per a suggestion by Jason Gunthorpe.
> ---
>  drivers/infiniband/sw/rxe/rxe_verbs.h | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

Applied to for-next

Thanks,
Jason

      reply	other threads:[~2023-06-20 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 17:16 [PATCH v2 for-next] RDMA/rxe: Fixes mr access supported list Bob Pearson
2023-06-20 14:44 ` 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=ZJG7a85CSnrkBlIQ@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.com \
    --cc=zyjzyj2000@gmail.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).