From: james.smart@broadcom.com (James Smart)
Subject: [PATCH v2 1/3] nvme-fabrics: allow discovery subsystems accept a kato
Date: Sun, 14 Jul 2019 08:00:07 -0700 [thread overview]
Message-ID: <81232ff3-15e5-5583-0459-8d044b581c47@broadcom.com> (raw)
In-Reply-To: <20190712180211.26333-2-sagi@grimberg.me>
On 7/12/2019 11:02 AM, Sagi Grimberg wrote:
> This modifies the behavior of discovery subsystems to accept
> a kato as a preparation to support discovery log change
> events. This also means that now every discovery controller
> will have a default kato value, and for non-persistent connections
> the host needs to pass in a zero kato value (keep_alive_tmo=0).
>
> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
> ---
> drivers/nvme/host/fabrics.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
>
Reviewed-by: James Smart <james.smart at broadcom.com>
next prev parent reply other threads:[~2019-07-14 15:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 18:02 [PATCH v2 0/3] Support discovery log change events Sagi Grimberg
2019-07-12 18:02 ` [PATCH v2 1/3] nvme-fabrics: allow discovery subsystems accept a kato Sagi Grimberg
2019-07-14 8:08 ` Minwoo Im
2019-07-14 15:00 ` James Smart [this message]
2019-07-19 13:48 ` Hannes Reinecke
2019-07-12 18:02 ` [PATCH v2 2/3] nvme: enable aen also for discovery controllers Sagi Grimberg
2019-07-14 8:09 ` Minwoo Im
2019-07-14 15:04 ` James Smart
2019-07-19 13:49 ` Hannes Reinecke
2019-07-12 18:02 ` [PATCH v2 3/3] nvme: fire discovery log page change events to userspace Sagi Grimberg
2019-07-14 8:14 ` Minwoo Im
2019-07-14 15:13 ` James Smart
2019-07-19 13:49 ` Hannes Reinecke
[not found] ` <20190822002328.GP9511@lst.de>
[not found] ` <205d06ab-fedc-739d-323f-b358aff2cbfe@grimberg.me>
[not found] ` <e4603511-6dae-e26d-12a9-e9fa727a8d03@grimberg.me>
[not found] ` <20190826065639.GA11036@lst.de>
[not found] ` <20190826075916.GA30396@kroah.com>
[not found] ` <ac168168-fed2-2b57-493e-e88261ead73b@grimberg.me>
[not found] ` <20190830055514.GC8492@lst.de>
2019-08-30 18:08 ` Sagi Grimberg
2019-08-30 18:36 ` James Smart
2019-08-30 21:07 ` Sagi Grimberg
2019-08-30 22:24 ` James Smart
2019-09-09 15:10 ` Hannes Reinecke
[not found] ` <20190830062036.GA15257@kroah.com>
2019-08-30 18:14 ` Sagi Grimberg
2019-09-02 19:33 ` Greg Kroah-Hartman
2019-09-04 1:35 ` Sagi Grimberg
2019-09-04 5:25 ` Greg Kroah-Hartman
2019-08-01 1:32 ` [PATCH v2 0/3] Support discovery log change events 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=81232ff3-15e5-5583-0459-8d044b581c47@broadcom.com \
--to=james.smart@broadcom.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).