From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: David Jeffery <djeffery@redhat.com>
Cc: linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
linux-pci@vger.kernel.org, linux-scsi@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
"Tarun Sahu" <tarunsahu@google.com>,
"Pasha Tatashin" <tatashin@google.com>,
"Michał Cłapiński" <mclapinski@google.com>,
"Jordan Richards" <jordanrichards@google.com>,
"Ewan Milne" <emilne@redhat.com>,
"John Meneghini" <jmeneghi@redhat.com>,
"Lombardi, Maurizio" <mlombard@redhat.com>,
"Stuart Hayes" <stuart.w.hayes@gmail.com>,
"Laurence Oberman" <loberman@redhat.com>,
"Bart Van Assche" <bvanassche@acm.org>,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"John Garry" <john.g.garry@oracle.com>
Subject: Re: [PATCH v14 0/5] shut down devices asynchronously
Date: Tue, 21 Apr 2026 20:42:02 -0400 [thread overview]
Message-ID: <yq1bjfbn7xl.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260420152608.6244-1-djeffery@redhat.com> (David Jeffery's message of "Mon, 20 Apr 2026 11:26:03 -0400")
David,
> This patchset allows the kernel to shutdown devices asynchronously and
> unrelated async devices to be shut down in parallel to each other.
>
> Only devices which explicitly enable it are shut down asynchronously.
> The default is for a device to be shut down from the synchronous
> shutdown loop.
>
> This can dramatically reduce system shutdown/reboot time on systems
> that have multiple devices that take many seconds to shut down (like
> certain NVMe drives). On one system tested, the shutdown time went
> from 11 minutes without this patch to 55 seconds with the patch. And
> on another system from 80 seconds to 11.
Looks OK to me.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen
prev parent reply other threads:[~2026-04-22 0:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 15:26 [PATCH v14 0/5] shut down devices asynchronously David Jeffery
2026-04-20 15:26 ` [PATCH 1/5] driver core: separate function to shutdown one device David Jeffery
2026-04-20 20:25 ` Pasha Tatashin
2026-04-20 15:26 ` [PATCH 2/5] driver core: do not always lock parent in shutdown David Jeffery
2026-04-20 15:26 ` [PATCH 3/5] driver core: async device shutdown infrastructure David Jeffery
2026-04-21 7:49 ` John Garry
2026-04-21 17:31 ` David Jeffery
2026-04-20 15:26 ` [PATCH 4/5] PCI: Enable async shutdown support David Jeffery
2026-04-20 15:26 ` [PATCH 5/5] scsi: " David Jeffery
2026-04-21 7:46 ` John Garry
2026-04-21 15:21 ` Pasha Tatashin
2026-04-21 8:01 ` [PATCH v14 0/5] shut down devices asynchronously John Garry
2026-04-21 13:30 ` David Jeffery
2026-04-22 0:42 ` Martin K. Petersen [this message]
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=yq1bjfbn7xl.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.org \
--cc=dakr@kernel.org \
--cc=djeffery@redhat.com \
--cc=driver-core@lists.linux.dev \
--cc=emilne@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=jmeneghi@redhat.com \
--cc=john.g.garry@oracle.com \
--cc=jordanrichards@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=mclapinski@google.com \
--cc=mlombard@redhat.com \
--cc=rafael@kernel.org \
--cc=stuart.w.hayes@gmail.com \
--cc=tarunsahu@google.com \
--cc=tatashin@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