From: Bob Pearson <rpearsonhpe@gmail.com>
To: jgg@nvidia.com, zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org,
frank.zago@hpe.com, jhack@hpe.com
Cc: Bob Pearson <rpearsonhpe@gmail.com>
Subject: [PATCH for-next 0/5] Fix incorrect atomic retry behavior
Date: Mon, 6 Jun 2022 09:38:32 -0500 [thread overview]
Message-ID: <20220606143836.3323-1-rpearsonhpe@gmail.com> (raw)
Restructure the design of the atomic retries in rxe_resp.c modeled
on the design of RDMA read reply. This fixes failures which
occur when an atomic ack packet is lost as observed in the
pyverbs test suite with a patch to randomly drop packets.
Link: https://lore.kernel.org/linux-rdma/84aaf934-9cac-30ae-0fa5-1e40819a519e@gmail.com/
Signed-off-by: Bob Pearson <rpearsonhpe@gmail.com>
---
Bob Pearson (5):
RDMA/rxe: Move code to rxe_prepare_atomic_res()
RDMA/rxe: Add a responder state for atomic reply
RDMA/rxe: Move atomic responder res to atomic_reply
RDMA/rxe: Move atomic original value to res
RDMA/rxe: Merge normal and retry atomic flows
drivers/infiniband/sw/rxe/rxe_qp.c | 2 -
drivers/infiniband/sw/rxe/rxe_resp.c | 132 ++++++++++++++++----------
drivers/infiniband/sw/rxe/rxe_verbs.h | 3 +-
3 files changed, 81 insertions(+), 56 deletions(-)
base-commit: f2906aa863381afb0015a9eb7fefad885d4e5a56
--
2.34.1
next reply other threads:[~2022-06-06 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 14:38 Bob Pearson [this message]
2022-06-06 14:38 ` [PATCH 1/5] RDMA/rxe: Move code to rxe_prepare_atomic_res() Bob Pearson
2022-06-06 14:38 ` [PATCH 2/5] RDMA/rxe: Add a responder state for atomic reply Bob Pearson
2022-06-06 14:38 ` [PATCH 3/5] RDMA/rxe: Move atomic responder res to atomic_reply Bob Pearson
2022-06-06 14:38 ` [PATCH 4/5] RDMA/rxe: Move atomic original value to res Bob Pearson
2022-06-06 14:38 ` [PATCH 5/5] RDMA/rxe: Merge normal and retry atomic flows Bob Pearson
2022-06-30 18:52 ` [PATCH for-next 0/5] Fix incorrect atomic retry behavior Jason Gunthorpe
2022-06-30 19:28 ` Bob Pearson
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=20220606143836.3323-1-rpearsonhpe@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=frank.zago@hpe.com \
--cc=jgg@nvidia.com \
--cc=jhack@hpe.com \
--cc=linux-rdma@vger.kernel.org \
--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