From: james_p_freyensee@linux.intel.com (Jay Freyensee)
Subject: [PATCH v3 0/4] sqsize fixes
Date: Tue, 16 Aug 2016 12:56:51 -0700 [thread overview]
Message-ID: <1471377415-29337-1-git-send-email-james_p_freyensee@linux.intel.com> (raw)
This patch series is based on making sure sqsize is defined as a
zero-based value throughout the code, per NVMe-over-Fabrics spec.
Changes from v2:
- patch 5, adding 1 to hrsqsize in target dropped
- using ...opts->queue_depth to set various queue sizes over sqsize.
Changes from v1:
- moved +1/+2 to outside le16_to_cpu() in patch 3 and 5
Changes from v0:
- found all the sqsize dependencies and adjusted them accordingly
- nvmf_connect_admin_queue() always uses NVMF_AQ_DEPTH for sqsize
- final patch to adjust hrqsize only, so the series can be easily
tested w/hrqsize == hrsqsize (patches 1-4) and hrqsize == hrsqsize+1
(patch 5)
Jay Freyensee (4):
nvmet-rdma: +1 to *queue_size from hsqsize/hrqsize
fabrics: define admin sqsize min default, per spec
nvme-rdma: fix sqsize/hsqsize per spec
nvme-loop: set sqsize to 0-based value, per spec
drivers/nvme/host/fabrics.c | 9 ++++++++-
drivers/nvme/host/rdma.c | 20 +++++++++++++++-----
drivers/nvme/target/loop.c | 4 ++--
drivers/nvme/target/rdma.c | 8 ++++----
4 files changed, 29 insertions(+), 12 deletions(-)
--
2.7.4
next reply other threads:[~2016-08-16 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 19:56 Jay Freyensee [this message]
2016-08-16 19:56 ` [PATCH v3 1/4] nvmet-rdma: +1 to *queue_size from hsqsize/hrqsize Jay Freyensee
2016-08-17 0:47 ` Christoph Hellwig
2016-08-17 14:49 ` Sagi Grimberg
2016-08-17 15:47 ` J Freyensee
2016-08-17 18:36 ` Sagi Grimberg
2016-08-17 18:51 ` J Freyensee
2016-08-16 19:56 ` [PATCH v3 2/4] fabrics: define admin sqsize min default, per spec Jay Freyensee
2016-08-16 19:56 ` [PATCH v3 3/4] nvme-rdma: fix sqsize/hsqsize " Jay Freyensee
2016-08-16 19:56 ` [PATCH v3 4/4] nvme-loop: set sqsize to 0-based value, " Jay Freyensee
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=1471377415-29337-1-git-send-email-james_p_freyensee@linux.intel.com \
--to=james_p_freyensee@linux.intel.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).