From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Keith Busch <keith.busch@intel.com>,
James Smart <james.smart@broadcom.com>,
Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 1/4] nvme-fabrics: allow discovery subsystems accept a kato
Date: Mon, 9 Sep 2019 16:47:59 +0000 [thread overview]
Message-ID: <BYAPR04MB57492B8AAE2A59F3A37E288486B70@BYAPR04MB5749.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20190904215954.15423-2-sagi@grimberg.me
Looks good to me, btw do we have existing test-case which
covers this behavior ?
Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
On 09/04/2019 03:00 PM, 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).
>
> Reviewed-by: Minwoo Im <minwoo.im.dev@gmail.com>
> Reviewed-by: James Smart <james.smart@broadcom.com>
> Reviewed-by: Hannes Reinecke <hare@suse.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> ---
> drivers/nvme/host/fabrics.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/nvme/host/fabrics.c b/drivers/nvme/host/fabrics.c
> index 145c210edb03..74b8818ac9a1 100644
> --- a/drivers/nvme/host/fabrics.c
> +++ b/drivers/nvme/host/fabrics.c
> @@ -381,8 +381,8 @@ int nvmf_connect_admin_queue(struct nvme_ctrl *ctrl)
> * Set keep-alive timeout in seconds granularity (ms * 1000)
> * and add a grace period for controller kato enforcement
> */
> - cmd.connect.kato = ctrl->opts->discovery_nqn ? 0 :
> - cpu_to_le32((ctrl->kato + NVME_KATO_GRACE) * 1000);
> + cmd.connect.kato = ctrl->kato ?
> + cpu_to_le32((ctrl->kato + NVME_KATO_GRACE) * 1000) : 0;
>
> if (ctrl->opts->disable_sqflow)
> cmd.connect.cattr |= NVME_CONNECT_DISABLE_SQFLOW;
> @@ -740,13 +740,6 @@ static int nvmf_parse_options(struct nvmf_ctrl_options *opts,
> pr_warn("keep_alive_tmo 0 won't execute keep alives!!!\n");
> }
> opts->kato = token;
> -
> - if (opts->discovery_nqn && opts->kato) {
> - pr_err("Discovery controllers cannot accept KATO != 0\n");
> - ret = -EINVAL;
> - goto out;
> - }
> -
> break;
> case NVMF_OPT_CTRL_LOSS_TMO:
> if (match_int(args, &token)) {
> @@ -883,7 +876,6 @@ static int nvmf_parse_options(struct nvmf_ctrl_options *opts,
> }
>
> if (opts->discovery_nqn) {
> - opts->kato = 0;
> opts->nr_io_queues = 0;
> opts->nr_write_queues = 0;
> opts->nr_poll_queues = 0;
>
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-09-09 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 21:59 [PATCH v4 0/4] Support discovery log change events Sagi Grimberg
2019-09-04 21:59 ` [PATCH v4 1/4] nvme-fabrics: allow discovery subsystems accept a kato Sagi Grimberg
2019-09-09 16:47 ` Chaitanya Kulkarni [this message]
2019-09-04 21:59 ` [PATCH v4 2/4] nvme: enable aen regardless of the presence of I/O queues Sagi Grimberg
2019-09-09 11:17 ` Hannes Reinecke
2019-09-09 16:48 ` Chaitanya Kulkarni
2019-09-04 21:59 ` [PATCH v4 3/4] nvme: add uevent variables for controller devices Sagi Grimberg
2019-09-04 23:17 ` James Smart
2019-09-05 0:18 ` Sagi Grimberg
2019-09-05 16:00 ` James Smart
2019-09-05 20:06 ` Sagi Grimberg
2019-09-06 12:59 ` Christoph Hellwig
2019-09-06 18:07 ` Sagi Grimberg
2019-09-09 11:18 ` Hannes Reinecke
2019-09-04 21:59 ` [PATCH v4 4/4] nvme: send discovery log page change events to userspace Sagi Grimberg
2019-09-06 13:00 ` Christoph Hellwig
2019-09-09 16:50 ` Chaitanya Kulkarni
2019-09-04 21:59 ` [PATCH v4 5/4 nvme-cli] udev: convert the discovery event handler to the kernel support 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=BYAPR04MB57492B8AAE2A59F3A37E288486B70@BYAPR04MB5749.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=keith.busch@intel.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).