public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Uday Shankar <ushankar@purestorage.com>
Cc: Costa Sapuntzakis <costa@purestorage.com>,
	Randy Jennings <randyj@purestorage.com>,
	Hannes Reinecke <hare@suse.de>, Sagi Grimberg <sagi@grimberg.me>,
	Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
	Jens Axboe <axboe@fb.com>,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH v5 2/3] nvme: check IO start time when deciding to defer KA
Date: Thu, 25 May 2023 11:16:28 +0200	[thread overview]
Message-ID: <20230525091628.GB26725@lst.de> (raw)
In-Reply-To: <20230524232218.1584605-3-ushankar@purestorage.com>

On Wed, May 24, 2023 at 05:22:17PM -0600, Uday Shankar wrote:
> +	if (ctrl->kas && req->deadline - req->timeout >= ctrl->ka_last_check_time)

Pleae avoid the overly long line.

> @@ -1173,6 +1179,7 @@ static unsigned long nvme_keep_alive_work_period(struct nvme_ctrl *ctrl)
>  	 */
>  	if (ctrl->ctratt & NVME_CTRL_ATTR_TBKAS)
>  		delay /= 2;
> +
>  	return delay;

Spurіous whitespace change.


  reply	other threads:[~2023-05-25  9:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 23:22 [PATCH v5 0/3] keepalive bugfixes Uday Shankar
2023-05-24 23:22 ` [PATCH v5 1/3] nvme: double KA polling frequency to avoid KATO with TBKAS on Uday Shankar
2023-05-25  9:15   ` Christoph Hellwig
2023-05-24 23:22 ` [PATCH v5 2/3] nvme: check IO start time when deciding to defer KA Uday Shankar
2023-05-25  9:16   ` Christoph Hellwig [this message]
2023-05-24 23:22 ` [PATCH v5 3/3] nvme: improve handling of long keep alives Uday Shankar
2023-05-25  9:16   ` Christoph Hellwig

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=20230525091628.GB26725@lst.de \
    --to=hch@lst.de \
    --cc=axboe@fb.com \
    --cc=costa@purestorage.com \
    --cc=hare@suse.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=randyj@purestorage.com \
    --cc=sagi@grimberg.me \
    --cc=ushankar@purestorage.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