Linux CXL
 help / color / mirror / Atom feed
From: <dan.j.williams@intel.com>
To: Michal Clapinski <mclapinski@google.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	"Dave Jiang" <dave.jiang@intel.com>, <nvdimm@lists.linux.dev>,
	<linux-cxl@vger.kernel.org>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
	<linux-kernel@vger.kernel.org>,
	Michal Clapinski <mclapinski@google.com>
Subject: Re: [PATCH v3 0/5] dax: add PROBE_PREFER_ASYNCHRONOUS to all the dax drivers
Date: Thu, 20 Nov 2025 16:58:55 -0800	[thread overview]
Message-ID: <691fb94f7aee9_1eb85100cd@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <20251024210518.2126504-1-mclapinski@google.com>

Michal Clapinski wrote:
> Comments in linux/device/driver.h say that the goal is to do async
> probing on all devices. The current behavior unnecessarily slows down
> the boot by synchronously probing dax devices, so let's change that.
> 
> For thousands of devices, this change saves >1s of boot time.
> 
> Michal Clapinski (5):
>   dax: add PROBE_PREFER_ASYNCHRONOUS to the pmem driver
>   dax: add PROBE_PREFER_ASYNCHRONOUS to the kmem driver
>   dax: add PROBE_PREFER_ASYNCHRONOUS to the cxl driver
>   dax: add PROBE_PREFER_ASYNCHRONOUS to the hmem drivers
>   dax: add PROBE_PREFER_ASYNCHRONOUS to the dax device driver

After seeing the trouble this causes with libdaxctl and failing to find
a quick fix I wonder if you should just go through route of eating the
potential regressions in your own environment.

I.e. instead of making it a problem that the kernel needs to debug for
all legacy users, how about you just boot with the command line option:

   driver_async_probe=device_dax

...or add the following to your mopdrobe configuration:

   options device_dax async_probe

I.e. do you really need to change this policy globally for everyone at
this point?

I do want to improve this, but I think it will take time for libdaxctl
to get ready for this flag day.

  parent reply	other threads:[~2025-11-21  0:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24 21:05 [PATCH v3 0/5] dax: add PROBE_PREFER_ASYNCHRONOUS to all the dax drivers Michal Clapinski
2025-10-24 21:05 ` [PATCH v3 1/5] dax: add PROBE_PREFER_ASYNCHRONOUS to the pmem driver Michal Clapinski
2025-10-24 21:05 ` [PATCH v3 2/5] dax: add PROBE_PREFER_ASYNCHRONOUS to the kmem driver Michal Clapinski
2025-10-24 21:05 ` [PATCH v3 3/5] dax: add PROBE_PREFER_ASYNCHRONOUS to the cxl driver Michal Clapinski
2025-10-24 21:05 ` [PATCH v3 4/5] dax: add PROBE_PREFER_ASYNCHRONOUS to the hmem drivers Michal Clapinski
2025-10-24 21:05 ` [PATCH v3 5/5] dax: add PROBE_PREFER_ASYNCHRONOUS to the dax device driver Michal Clapinski
2025-11-18 21:48   ` Ira Weiny
2025-11-20 17:11     ` Michał Cłapiński
2025-11-21  0:48       ` Ira Weiny
2025-10-24 23:05 ` [PATCH v3 0/5] dax: add PROBE_PREFER_ASYNCHRONOUS to all the dax drivers dan.j.williams
2025-10-27 15:52 ` Dave Jiang
2025-11-14 12:24 ` Michał Cłapiński
2025-11-21  0:58 ` dan.j.williams [this message]
2025-11-21 16:33   ` Michał Cłapiński

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=691fb94f7aee9_1eb85100cd@dwillia2-mobl4.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mclapinski@google.com \
    --cc=nvdimm@lists.linux.dev \
    --cc=pasha.tatashin@soleen.com \
    --cc=vishal.l.verma@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