From: hch@infradead.org (Christoph Hellwig)
Subject: NVMe over fabrics - Caching controller Identity data
Date: Wed, 19 Apr 2017 22:47:09 -0700 [thread overview]
Message-ID: <20170420054709.GB18181@infradead.org> (raw)
In-Reply-To: <603f53f6-1211-3b5f-31c8-dfa1e8700c26@oracle.com>
On Fri, Apr 14, 2017@10:49:10AM -0700, Steve Blightman wrote:
> As I understand it, the linux initiator caches the controller Identity data
> and some other values. These only get loaded when it first connects, or
> when the controller is reset. Now If a target wishes to change any of these
> values, capsule size for instance, it might set the new values and restart
> itself, but when the initiator reconnects to an existing controller, it
> still has the old values. Is there a way for the target to force the
> initiator to reload these values somehow?
Identify controller is supposed to be static data for a controller.
If your controller has changed you need to reject the reconnect and
present a new controller.
next prev parent reply other threads:[~2017-04-20 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 17:49 NVMe over fabrics - Caching controller Identity data Steve Blightman
2017-04-20 5:47 ` Christoph Hellwig [this message]
2017-04-20 11:46 ` Sagi Grimberg
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=20170420054709.GB18181@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;
as well as URLs for NNTP newsgroup(s).