From: hch@infradead.org (Christoph Hellwig)
Subject: Q: nvme_rdma and reconnect
Date: Thu, 22 Dec 2016 04:10:19 -0800 [thread overview]
Message-ID: <20161222121019.GA22558@infradead.org> (raw)
In-Reply-To: <9576f8bf-e2df-d00f-edb6-8f17ae188980@grimberg.me>
On Thu, Dec 22, 2016@02:08:44PM +0200, Sagi Grimberg wrote:
> We can go via the same flow and condition on the state for the
> differences, but I'm not sure its easier to understand than two
> distinct routines (although that share a lot of code).
FYI, my attempt back then was to have a shutdown and a connect
method that these two path call, with the hope of folding the initial
connect and final shutdown into it as well, similar to how the PCI
code work.
next prev parent reply other threads:[~2016-12-22 12:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 18:39 [PATCH] nvmet: fix KATO offset in Set Features Daniel Verkamp
2016-12-07 19:09 ` Daniel Verkamp
2016-12-09 18:28 ` Christoph Hellwig
2016-12-09 20:04 ` Daniel Verkamp
2016-12-21 10:27 ` Christoph Hellwig
[not found] ` <830460a5-ce31-b882-8f06-4a906763eb50@broadcom.com>
2016-12-22 6:41 ` Q: nvme_rdma and reconnect Christoph Hellwig
2016-12-22 12:08 ` Sagi Grimberg
2016-12-22 12:10 ` Christoph Hellwig [this message]
2016-12-22 12:52 ` Sagi Grimberg
2016-12-22 12:46 ` Hannes Reinecke
2016-12-22 12:50 ` Christoph Hellwig
2016-12-09 19:59 ` [PATCH v2] nvmet: fix KATO offset in Set Features Daniel Verkamp
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=20161222121019.GA22558@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).