From: jgg@ziepe.ca (Jason Gunthorpe)
Subject: [PATCH 0/3] Fix request completion holes
Date: Wed, 1 Nov 2017 10:50:36 -0600 [thread overview]
Message-ID: <20171101165036.GD1030@ziepe.ca> (raw)
In-Reply-To: <d9dcdb05-d001-53d8-7ed7-5fafc1709f4a@mellanox.com>
On Wed, Nov 01, 2017@06:02:38PM +0200, idanb wrote:
> (3) No send signal with invalidation signal w/o moderation 5.2M / 8.3M
Actually, isn't this valid and reasonable? You don't need to see the
SEND completion, the only thing that matters is the invalidate
completion, and the invalidate will naturally order after the send
is finished, yes?
Jason
next prev parent reply other threads:[~2017-11-01 16:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 8:55 [PATCH 0/3] Fix request completion holes Sagi Grimberg
2017-10-31 8:55 ` [PATCH 1/3] nvme-rdma: don't suppress send completions Sagi Grimberg
2017-10-31 8:55 ` [PATCH 2/3] nvme-rdma: don't complete requests before a send work request has completed Sagi Grimberg
2017-10-31 8:55 ` [PATCH 3/3] nvme-rdma: wait for local invalidation before completing a request Sagi Grimberg
2017-10-31 9:38 ` [PATCH 0/3] Fix request completion holes Max Gurtovoy
2017-10-31 11:10 ` Sagi Grimberg
2017-11-01 16:02 ` idanb
2017-11-01 16:09 ` Max Gurtovoy
2017-11-01 16:50 ` Jason Gunthorpe [this message]
2017-11-01 17:31 ` Sagi Grimberg
2017-11-01 17:58 ` Jason Gunthorpe
2017-11-02 8:06 ` Sagi Grimberg
2017-11-02 15:12 ` Jason Gunthorpe
2017-11-02 15:23 ` Sagi Grimberg
2017-11-02 15:51 ` Jason Gunthorpe
2017-11-02 16:15 ` Sagi Grimberg
2017-11-02 16:18 ` Steve Wise
2017-11-02 16:36 ` Jason Gunthorpe
2017-11-02 16:53 ` Steve Wise
2017-11-02 16:54 ` Jason Gunthorpe
2017-11-01 17:26 ` Sagi Grimberg
2017-11-01 22:23 ` Max Gurtovoy
2017-11-02 17:55 ` Steve Wise
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=20171101165036.GD1030@ziepe.ca \
--to=jgg@ziepe.ca \
/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).