Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v2] nvmet: discovery controller to set ioccsz and iorcsz
Date: Fri, 17 Feb 2017 01:15:32 -0800	[thread overview]
Message-ID: <20170217091532.GA16652@infradead.org> (raw)
In-Reply-To: <58a6630c.QwbzGsQTsh8C63rk%jsmart2021@gmail.com>

On Thu, Feb 16, 2017@06:42:20PM -0800, James Smart wrote:
> 
> Revised the patch: add transport capsule inline size into ioccsz value
> 
> The discovery controller's Identify command handler never set these
> fields leaving them zero. The host-side fc transport validates that
> these values are appropriate and was killing the connection with the
> controller as they were zero.
> 
> Set the controller ioccsz and iorcsz values

Discovery controllers do not support I/O commands, so these settings
don't make any sense there.  They are also not included in the
fields that Idenitfy Controller should report for Discovery controllers
(Figure 33 in Fabrics 1.0)

  reply	other threads:[~2017-02-17  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17  2:42 [PATCH v2] nvmet: discovery controller to set ioccsz and iorcsz James Smart
2017-02-17  9:15 ` Christoph Hellwig [this message]
2017-02-21 20:41   ` J 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=20170217091532.GA16652@infradead.org \
    --to=hch@infradead.org \
    /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