From: Greg KH <gregkh@linuxfoundation.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Keith Busch <keith.busch@intel.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] nvme: Boot as soon as the boot controller has been probed
Date: Sun, 8 Nov 2020 09:24:03 +0100 [thread overview]
Message-ID: <20201108082403.GB40741@kroah.com> (raw)
In-Reply-To: <20201108040903.8185-1-bvanassche@acm.org>
On Sat, Nov 07, 2020 at 08:09:03PM -0800, Bart Van Assche wrote:
> The following two issues have been introduced by commit 1811977568e0
> ("nvme/pci: Use async_schedule for initial reset work"):
> - The boot process waits until all NVMe controllers have been probed
> instead of only waiting until the boot controller has been probed.
> This slows down the boot process.
> - Some of the controller probing work happens asynchronously without
> the device core being aware of this.
>
> Hence this patch that makes all probing work happen from nvme_probe()
> and that tells the device core to probe multiple NVMe controllers
> concurrently by setting PROBE_PREFER_ASYNCHRONOUS.
>
> Cc: Mikulas Patocka <mpatocka@redhat.com>
> Cc: Keith Busch <keith.busch@intel.com>
> Cc: Greg KH <gregkh@linuxfoundation.org>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
A fixes: tag?
thanks,
greg k-h
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-11-08 8:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 4:09 [PATCH] nvme: Boot as soon as the boot controller has been probed Bart Van Assche
2020-11-08 8:24 ` Greg KH [this message]
2020-11-08 22:31 ` Keith Busch
2020-11-08 23:35 ` Bart Van Assche
2020-11-09 2:35 ` Keith Busch
2020-11-09 4:00 ` Bart Van Assche
2020-11-09 15:05 ` Keith Busch
2020-11-10 2:51 ` Bart Van Assche
2020-11-10 3:12 ` Keith Busch
2020-11-08 19:13 ` Sagi Grimberg
2020-11-08 19:18 ` Greg KH
2020-11-08 23:00 ` Bart Van Assche
2020-11-09 3:04 ` Keith Busch
2020-11-11 19:19 ` Keith Busch
2020-11-12 4:26 ` Bart Van Assche
2020-11-12 14:20 ` Keith Busch
2020-11-19 3:08 ` Bart Van Assche
2020-11-19 20:18 ` 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=20201108082403.GB40741@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mpatocka@redhat.com \
--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