From: hch@lst.de (Christoph Hellwig)
Subject: Disconnecting nvmet-rdma
Date: Fri, 21 Oct 2016 15:39:38 +0200 [thread overview]
Message-ID: <20161021133938.GB19067@lst.de> (raw)
In-Reply-To: <fe8993ab-38c9-96a1-0c75-e018de246107@grimberg.me>
On Thu, Oct 20, 2016@10:49:43AM +0300, Sagi Grimberg wrote:
> Where do you see indication for that in the code? TIMEWAIT doesn't make
> sense for listener cm_ids.
Nowhere, this was just a wild guess given the pain we had with these
listener IDs before.
next prev parent reply other threads:[~2016-10-21 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 22:02 Disconnecting nvmet-rdma Bart Van Assche
2016-10-19 13:00 ` Christoph Hellwig
2016-10-20 7:49 ` Sagi Grimberg
2016-10-21 13:39 ` Christoph Hellwig [this message]
2016-10-21 15:21 ` Bart Van Assche
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=20161021133938.GB19067@lst.de \
--to=hch@lst.de \
/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