From: Alexander Duyck <alexander.h.duyck@linux.intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
linux-nvdimm@lists.01.org, tj@kernel.org,
akpm@linux-foundation.org, linux-pm@vger.kernel.org,
jiangshanlai@gmail.com, rafael@kernel.org, len.brown@intel.com,
pavel@ucw.cz, zwisler@kernel.org, dan.j.williams@intel.com,
dave.jiang@intel.com, bvanassche@acm.org
Subject: Re: [driver-core PATCH v8 0/9] Add NUMA aware async_schedule calls
Date: Mon, 10 Dec 2018 15:25:04 -0800 [thread overview]
Message-ID: <dd0b44d5dd9d19ac6735f80ae66bb437ec55b2cf.camel@linux.intel.com> (raw)
In-Reply-To: <20181210192216.GJ28501@garbanzo.do-not-panic.com>
On Mon, 2018-12-10 at 11:22 -0800, Luis Chamberlain wrote:
> On Wed, Dec 05, 2018 at 09:25:13AM -0800, Alexander Duyck wrote:
> > This patch set provides functionality that will help to improve the
> > locality of the async_schedule calls used to provide deferred
> > initialization.
> >
> > This patch set originally started out focused on just the one call to
> > async_schedule_domain in the nvdimm tree that was being used to defer the
> > device_add call however after doing some digging I realized the scope of
> > this was much broader than I had originally planned. As such I went
> > through and reworked the underlying infrastructure down to replacing the
> > queue_work call itself with a function of my own and opted to try and
> > provide a NUMA aware solution that would work for a broader audience.
> >
> > In addition I have added several tweaks and/or clean-ups to the front of the
> > patch set. Patches 1 through 4 address a number of issues that actually were
> > causing the existing async_schedule calls to not show the performance that
> > they could due to either not scaling on a per device basis, or due to issues
> > that could result in a potential deadlock. For example, patch 4 addresses the
> > fact that we were calling async_schedule once per driver instead of once
> > per device, and as a result we would have still ended up with devices
> > being probed on a non-local node without addressing this first.
>
> No tests were added. Again, I think it would be good to add test
> cases to showcase the old mechanisms, illustrate the new, and ensure
> we don't regress both now and also help us ensure we don't regress
> moving forward.
>
> This is all too critical of a path for the kernel, and these changes
> are rather instrusive. I'd readlly like to see test code for it now
> rather than later.
>
> Luis
Sorry about that. I was more focused on the rewrite of patch 2 and
overlooked the comment about lib/test_kmod.c.
I'll look into it and see if I can squeeze it in for v9.
Thanks.
- Alex
next prev parent reply other threads:[~2018-12-10 23:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 17:25 [driver-core PATCH v8 0/9] Add NUMA aware async_schedule calls Alexander Duyck
2018-12-05 17:25 ` [driver-core PATCH v8 1/9] driver core: Move async_synchronize_full call Alexander Duyck
2018-12-05 17:25 ` [driver-core PATCH v8 2/9] driver core: Establish order of operations for device_add and device_del via bitflag Alexander Duyck
2018-12-10 18:58 ` Dan Williams
[not found] ` <CAPcyv4jH_Op-xHTd2FwQizPaWFx_2FE-pVsOLLmZAEK8EVPrYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-10 19:35 ` Alexander Duyck
2018-12-10 19:43 ` Dan Williams
[not found] ` <CAPcyv4i1RTrKYX0YpyCRE=pqt3pHBRiCGQq1wYUriLjKKTVA7A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-10 20:57 ` Alexander Duyck
[not found] ` <bd92d0a3ff60097bf4424ff4c556a5369e66da6d.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2018-12-10 21:15 ` Dan Williams
2018-12-10 21:23 ` Dan Williams
[not found] ` <CAPcyv4hrML3SKnFP9UANC-hdTrpnOx4nWX=b-yhLsLuujL5oAA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-10 22:24 ` Alexander Duyck
[not found] ` <00810f93b199c524378b5c963d49bd798c5d9843.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2018-12-10 22:41 ` Dan Williams
2018-12-05 17:25 ` [driver-core PATCH v8 3/9] device core: Consolidate locking and unlocking of parent and device Alexander Duyck
2018-12-05 17:25 ` [driver-core PATCH v8 4/9] driver core: Probe devices asynchronously instead of the driver Alexander Duyck
2018-12-05 17:25 ` [driver-core PATCH v8 5/9] workqueue: Provide queue_work_node to queue work near a given NUMA node Alexander Duyck
2018-12-05 17:25 ` [driver-core PATCH v8 6/9] async: Add support for queueing on specific " Alexander Duyck
2018-12-05 17:25 ` [driver-core PATCH v8 7/9] driver core: Attach devices on CPU local to device node Alexander Duyck
2018-12-05 17:25 ` [driver-core PATCH v8 8/9] PM core: Use new async_schedule_dev command Alexander Duyck
2018-12-05 17:26 ` [driver-core PATCH v8 9/9] libnvdimm: Schedule device registration on node local to the device Alexander Duyck
2018-12-10 19:22 ` [driver-core PATCH v8 0/9] Add NUMA aware async_schedule calls Luis Chamberlain
2018-12-10 23:25 ` Alexander Duyck [this message]
[not found] ` <dd0b44d5dd9d19ac6735f80ae66bb437ec55b2cf.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2018-12-10 23:35 ` Luis Chamberlain
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=dd0b44d5dd9d19ac6735f80ae66bb437ec55b2cf.camel@linux.intel.com \
--to=alexander.h.duyck@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-pm@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=tj@kernel.org \
--cc=zwisler@kernel.org \
/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