linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: james_p_freyensee@linux.intel.com (Jay Freyensee)
Subject: [PATCH 0/2] nvme-fabrics: sqsize bug fixes
Date: Fri,  5 Aug 2016 17:54:09 -0700	[thread overview]
Message-ID: <1470444851-7459-1-git-send-email-james_p_freyensee@linux.intel.com> (raw)

A few sqsize bugs have been discovered during the connect()
operation, basically the NVMe-fabrics layer being not-in-sync
with the implementation layer (RDMA).

As these bugs actually do break the NVMe-Fabrics spec, I'd like
to make the request to apply these fixes to the 4.8 kernel
(when approved).

Jay Freyensee (2):
  nvme-rdma: tell fabrics layer admin queue depth
  nvme-rdma: sqsize/hsqsize/hrqsize is 0-based val

 drivers/nvme/host/fabrics.c |  2 +-
 drivers/nvme/host/nvme.h    |  1 +
 drivers/nvme/host/rdma.c    | 20 +++++++++++++++++---
 3 files changed, 19 insertions(+), 4 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-08-06  0:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06  0:54 Jay Freyensee [this message]
2016-08-06  0:54 ` [PATCH 1/2] nvme-rdma: tell fabrics layer admin queue depth Jay Freyensee
2016-08-07  7:20   ` Sagi Grimberg
2016-08-08  7:05     ` Christoph Hellwig
2016-08-08 16:11       ` J Freyensee
2016-08-06  0:54 ` [PATCH 2/2] nvme-rdma: sqsize/hsqsize/hrqsize is 0-based val Jay Freyensee
2016-08-07  7:29   ` Sagi Grimberg
2016-08-08  7:06     ` Christoph Hellwig
2016-08-08 16:30       ` Verkamp, Daniel
     [not found]         ` <9A947B1F6D0FF74CB5D6ACFF43B473F3A3A45C75@ORSMSX112.amr.corp.intel.com>
2016-08-08 18:39           ` J Freyensee
2016-08-08 16:08     ` Verkamp, Daniel

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=1470444851-7459-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).