From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Keith Busch <kbusch@fb.com>,
linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCH] nvme: do not update kato from a dsm io command
Date: Fri, 12 Aug 2022 07:33:30 +0200 [thread overview]
Message-ID: <20220812053329.GA24588@lst.de> (raw)
In-Reply-To: <YvVgIzRXRv6EKk98@kbusch-mbp.dhcp.thefacebook.com>
On Thu, Aug 11, 2022 at 02:01:39PM -0600, Keith Busch wrote:
> Actually please disregard this. We don't reach the effects_end on io commands
> as it is already.
I thought we do, what prevents them from ending up there?
And we really should be more careful on admin vs I/O commands here
anyway.
next prev parent reply other threads:[~2022-08-12 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 19:26 [PATCH] nvme: do not update kato from a dsm io command Keith Busch
2022-08-11 20:01 ` Keith Busch
2022-08-12 5:33 ` Christoph Hellwig [this message]
2022-08-12 14:46 ` Keith Busch
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=20220812053329.GA24588@lst.de \
--to=hch@lst.de \
--cc=kbusch@fb.com \
--cc=kbusch@kernel.org \
--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