From: Alexander Duyck <firstname.lastname@example.org> To: email@example.com, firstname.lastname@example.org Cc: email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Subject: [driver-core PATCH v4 0/6] Add NUMA aware async_schedule calls Date: Mon, 15 Oct 2018 08:09:01 -0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) 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 with me 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. RFC->v1: Dropped nvdimm patch to submit later It relies on code in libnvdimm development tree Simplified queue_work_near to just convert node into a CPU Split up drivers core and PM core patches v1->v2: Renamed queue_work_near to queue_work_node Added WARN_ON_ONCE if we use queue_work_node with per-cpu workqueue v2->v3: Added Acked-by for queue_work_node patch Continued rename from _near to _node to be consistent with queue_work_node Renamed async_schedule_near_domain to async_schedule_node_domain Renamed async_schedule_near to async_schedule_node Added kerneldoc for new async_schedule_XXX functions Updated patch description for patch 4 to include data on potential gains v3->v4 Added patch to consolidate use of need_parent_lock Make asynchronous driver probing explicit about use of drvdata Added Acked-by for PM core patch --- Alexander Duyck (6): workqueue: Provide queue_work_node to queue work near a given NUMA node async: Add support for queueing on specific NUMA node device core: Consolidate locking and unlocking of parent and device driver core: Probe devices asynchronously instead of the driver driver core: Attach devices on CPU local to device node PM core: Use new async_schedule_dev command drivers/base/base.h | 2 + drivers/base/bus.c | 46 ++-------------- drivers/base/dd.c | 130 ++++++++++++++++++++++++++++++++++++++++----- drivers/base/power/main.c | 12 ++-- include/linux/async.h | 84 ++++++++++++++++++++++++++++- include/linux/device.h | 4 + include/linux/workqueue.h | 2 + kernel/async.c | 53 ++++++++++-------- kernel/workqueue.c | 84 +++++++++++++++++++++++++++++ 9 files changed, 329 insertions(+), 88 deletions(-) --
next reply other threads:[~2018-10-15 15:09 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-15 15:09 Alexander Duyck [this message] 2018-10-15 15:09 ` [driver-core PATCH v4 1/6] workqueue: Provide queue_work_node to queue work near a given NUMA node Alexander Duyck 2018-10-15 15:09 ` [driver-core PATCH v4 2/6] async: Add support for queueing on specific " Alexander Duyck 2018-10-15 15:09 ` [driver-core PATCH v4 3/6] device core: Consolidate locking and unlocking of parent and device Alexander Duyck 2018-10-18 7:46 ` Rafael J. Wysocki 2018-10-18 17:53 ` Bart Van Assche 2018-10-15 15:09 ` [driver-core PATCH v4 4/6] driver core: Probe devices asynchronously instead of the driver Alexander Duyck 2018-10-18 18:11 ` Bart Van Assche 2018-10-18 19:38 ` Alexander Duyck 2018-10-18 20:13 ` Bart Van Assche 2018-10-19 2:20 ` Alexander Duyck 2018-10-19 2:31 ` Bart Van Assche 2018-10-19 22:35 ` Alexander Duyck 2018-10-15 15:09 ` [driver-core PATCH v4 5/6] driver core: Attach devices on CPU local to device node Alexander Duyck 2018-10-15 15:09 ` [driver-core PATCH v4 6/6] PM core: Use new async_schedule_dev command Alexander Duyck
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [driver-core PATCH v4 0/6] Add NUMA aware async_schedule calls' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).