From: Christoph Hellwig <hch@lst.de>
To: Jeremy Allison <jallison@ciq.com>
Cc: jra@samba.org, tansuresh@google.com, hch@lst.de,
linux-nvme@lists.infradead.org, gregkh@linuxfoundation.org,
rafael@kernel.org, bhelgaas@google.com
Subject: Re: [PATCH 3/3] nvme: Add async shutdown support
Date: Tue, 19 Dec 2023 06:43:49 +0100 [thread overview]
Message-ID: <20231219054349.GA892@lst.de> (raw)
In-Reply-To: <20231215000358.1203338-4-jallison@ciq.com>
On Thu, Dec 14, 2023 at 04:03:58PM -0800, Jeremy Allison wrote:
> From: Tanjore Suresh <tansuresh@google.com>
>
> This works with the asynchronous shutdown mechanism setup for the PCI
> drivers and participates to provide both pre and post shutdown
> routines at pci_driver structure level.
>
> The shutdown_pre routine starts the shutdown and does not wait for the
> shutdown to complete. The shutdown_post routine waits for the shutdown
> to complete on individual controllers that this driver instance
> controls. This mechanism optimizes to speed up the shutdown in a
> system which host many controllers.
I had a really hard time trying to understand this patch.
Please split switching from the bool shutdown to an enum (with initially
just two values) into a separate patch. And the names really confuse
me. I would have expect something like:
NVME_DISABLE_RESET,
NVME_DISABLE_SHUTDOWN_SYNC,
NVME_DISABLE_SHUTDOWN_ASYNC,
then again mixing two rather different concept (reset vs shutdown)
into a single enum is also not very helpful (but neither would be
two bool arguments). Not really sure what the right thing is, but
as-is it feels pretty obfuscated.
next prev parent reply other threads:[~2023-12-19 5:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 0:03 Make NVME shutdown async - version 2 Jeremy Allison
2023-12-15 0:03 ` [PATCH 1/3] driver core: Support asynchronous driver shutdown Jeremy Allison
2023-12-15 12:21 ` Greg KH
2023-12-19 5:33 ` Christoph Hellwig
2023-12-19 6:19 ` Jeremy Allison
2023-12-19 6:21 ` Christoph Hellwig
2023-12-19 13:49 ` Sagi Grimberg
2023-12-19 13:56 ` Christoph Hellwig
2023-12-19 14:12 ` Sagi Grimberg
2023-12-15 0:03 ` [PATCH 2/3] PCI: Support asynchronous shutdown Jeremy Allison
2023-12-15 0:03 ` [PATCH 3/3] nvme: Add async shutdown support Jeremy Allison
2023-12-19 5:43 ` Christoph Hellwig [this message]
2023-12-19 6:35 ` Jeremy Allison
-- strict thread matches above, loose matches on Subject: below --
2023-12-12 18:09 Make NVME shutdown async Jeremy Allison
2023-12-12 18:09 ` [PATCH 3/3] nvme: Add async shutdown support Jeremy Allison
2022-03-24 21:42 Tanjore Suresh
2022-03-25 5:30 ` 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=20231219054349.GA892@lst.de \
--to=hch@lst.de \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jallison@ciq.com \
--cc=jra@samba.org \
--cc=linux-nvme@lists.infradead.org \
--cc=rafael@kernel.org \
--cc=tansuresh@google.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