From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 0/3] Fix request completion holes
Date: Tue, 31 Oct 2017 13:10:10 +0200 [thread overview]
Message-ID: <a950a671-22a1-432c-555e-8309c8a64a88@grimberg.me> (raw)
In-Reply-To: <8abcde91-9150-2982-3900-078619bcdac0@mellanox.com>
> Thanks Sagi.
> We'll run these patches in our lab + our patches for the performance
> improvments that we sent few days ago and update the results.
Thanks,
> I guess I'll need to run it with my cq moderation patches to get less
> penalty in performance.
Fine, but just a heads up, any cq moderation that is not adaptive is not
something
that we'd like to pursue. I have a generic adaptive moderation library
in the
works, so any ideas should be integrated into that (or something
equivalent).
next prev parent reply other threads:[~2017-10-31 11:10 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 [this message]
2017-11-01 16:02 ` idanb
2017-11-01 16:09 ` Max Gurtovoy
2017-11-01 16:50 ` Jason Gunthorpe
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=a950a671-22a1-432c-555e-8309c8a64a88@grimberg.me \
--to=sagi@grimberg.me \
/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).