From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] NVMe: Async probe
Date: Thu, 12 Feb 2015 15:25:26 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1502121509040.15481@localhost.lm.intel.com> (raw)
In-Reply-To: <005001d046d3$7f94b400$7ebe1c00$@samsung.com>
On Thu, 12 Feb 2015, Indraneel Mukherjee wrote:
>> static void nvme_reset_notify(struct pci_dev *pdev, bool prepare) @@
> -2902,6
>> +2906,7 @@ static void nvme_remove(struct pci_dev *pdev)
>> spin_unlock(&dev_list_lock);
>>
>> pci_set_drvdata(pdev, NULL);
>> + async_synchronize_cookie(dev->probe_cookie);
>
> Keith, I think this may not work. All asynchronous functions called prior to
> the one identified by cookie
> are guaranteed to have completed. The current one is not.
Huh, so it is. That rules out asynchronous_schedule as being useful
here. Workqueues FTW, then.
> And I just remembered Matthew's feedback on one of the previous attempts at
> asynchronous probe.
> We should be able to rmmod the driver during probe if suppose there are a
> million namespaces.
> Is there any plan to address such scenarios?
This idea would have allowed that if sync cookie worked like I'd
thought. The rmmod would just synchronize with the namespace discovery
first. I think we can use the global work queue and flush individual
work items in the remove path.
prev parent reply other threads:[~2015-02-12 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 1:11 [PATCH] linux-nvme 3.20 plans Keith Busch
2015-02-12 1:11 ` [PATCH] NVMe: Async probe Keith Busch
2015-02-12 14:52 ` Indraneel Mukherjee
2015-02-12 15:25 ` Keith Busch [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=alpine.LNX.2.00.1502121509040.15481@localhost.lm.intel.com \
--to=keith.busch@intel.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