From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
Subject: [PATCH RFC] nvme-rdma: support devices with queue size < 32
Date: Wed, 29 Mar 2017 10:27:51 -0600 [thread overview]
Message-ID: <20170329162751.GA7113@obsidianresearch.com> (raw)
In-Reply-To: <406682b9-d7ca-4718-5830-7940d2822bc0@grimberg.me>
On Wed, Mar 29, 2017@06:47:54PM +0300, Sagi Grimberg wrote:
> For each I/O we post up to 2 work requests, 1 for memory registration
> and 1 for sending an I/O request (and 1 for local invalidation if the
> target doesn't do it for us, but that is not the case here). So if our
> queue depth is X, we size our completion queue to be X*3, and we need
> to make sure we signal every (X*3)/2.
??? If your SQ is X and your CQ is X*3 you need to signal at X/2.
Jason
next prev parent reply other threads:[~2017-03-29 16:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 9:04 [PATCH RFC] nvme-rdma: support devices with queue size < 32 Marta Rybczynska
2017-03-23 9:24 ` Marta Rybczynska
2017-03-23 14:00 ` Christoph Hellwig
2017-03-23 14:36 ` Marta Rybczynska
2017-03-28 11:09 ` Sagi Grimberg
2017-03-28 11:20 ` Marta Rybczynska
2017-03-28 11:30 ` Sagi Grimberg
2017-03-29 9:36 ` Marta Rybczynska
2017-03-29 13:29 ` Jason Gunthorpe
2017-03-29 15:47 ` Sagi Grimberg
2017-03-29 16:27 ` Jason Gunthorpe [this message]
2017-03-29 16:39 ` Sagi Grimberg
2017-03-29 16:44 ` Doug Ledford
2017-03-29 16:47 ` Doug Ledford
2017-03-29 16:59 ` Sagi Grimberg
2017-03-29 22:19 ` Jason Gunthorpe
2017-03-30 14:23 ` Marta Rybczynska
2017-04-06 12:29 ` Marta Rybczynska
2017-04-06 13:02 ` Leon Romanovsky
2017-04-07 13:31 ` Marta Rybczynska
2017-04-09 12:31 ` Sagi Grimberg
2017-04-10 11:29 ` Marta Rybczynska
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=20170329162751.GA7113@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.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).