From: Bob Pearson <rpearsonhpe@gmail.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org,
frank.zago@hpe.com, jhack@hpe.com
Subject: Re: [PATCH for-next 0/5] Fix incorrect atomic retry behavior
Date: Thu, 30 Jun 2022 14:28:53 -0500 [thread overview]
Message-ID: <49cdb36d-3710-bdcd-7b8c-5edfeb93b36d@gmail.com> (raw)
In-Reply-To: <20220630185224.GA1055414@nvidia.com>
On 6/30/22 13:52, Jason Gunthorpe wrote:
> On Mon, Jun 06, 2022 at 09:38:32AM -0500, Bob Pearson wrote:
>> 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.
>
> Applied to for-next
>
> Thanks,
> Jason
Thanks.
I think this will commute with the other fixes I just sent. If it doesn't I can rebase them.
Bob
prev parent reply other threads:[~2022-06-30 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 14:38 [PATCH for-next 0/5] Fix incorrect atomic retry behavior Bob Pearson
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 [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=49cdb36d-3710-bdcd-7b8c-5edfeb93b36d@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