From: Daniel Jordan <daniel.m.jordan@oracle.com> To: linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: aaron.lu@intel.com, akpm@linux-foundation.org, dave.hansen@linux.intel.com, mgorman@techsingularity.net, mhocko@kernel.org, mike.kravetz@oracle.com, pasha.tatashin@oracle.com, steven.sistare@oracle.com, tim.c.chen@intel.com Subject: [RFC PATCH v3 0/7] ktask: multithread CPU-intensive kernel work Date: Tue, 5 Dec 2017 14:52:13 -0500 [thread overview] Message-ID: <20171205195220.28208-1-daniel.m.jordan@oracle.com> (raw) What do people think of the overall design and direction? There's documentation describing the design in the first patch of the series and the second patch has the API in ktask.h. Thanks, Daniel Changelog: v2 -> v3: - Changed cpu to CPU in the ktask Documentation, as suggested by Randy Dunlap - Saved more boot time now that Pavel Tatashin's deferred struct page init patches are in mainline (https://lkml.org/lkml/2017/10/13/692). New performance results in patch 7. - Added resource limits, per-node and system-wide, to maintain efficient concurrency levels (addresses a concern from my Plumbers talk) - ktask no longer allocates memory internally during a task so it can be used in sensitive contexts - Added the option to run work anywhere on the system rather than always confining it to a specific node - Updated Documentation patch with these changes and reworked motivation section v1 -> v2: - Added deferred struct page initialization use case. - Explained the source of the performance improvement from parallelizing clear_gigantic_page (comment from Dave Hansen). - Fixed Documentation and build warnings from CONFIG_KTASK=n kernels. My Linux Plumbers Unconference Talk: https://www.linuxplumbersconf.org/2017/ocw/proposals/4837 (please ignore OpenID's misapprehension that James Bottomley was speaker) ktask is a generic framework for parallelizing CPU-intensive work in the kernel. The intended use is for big machines that can use their CPU power to speed up large tasks that can't otherwise be multithreaded in userland. The API is generic enough to add concurrency to many different kinds of tasks--for example, zeroing a range of pages or evicting a list of inodes--and aims to save its clients the trouble of splitting up the work, choosing the number of threads to use, starting these threads, and load balancing the work between them. This patchset is based on 4.15-rc2 plus one mmots fix[*] and contains three ktask users: - deferred struct page initialization at boot time - clearing gigantic pages - fallocate for HugeTLB pages Work in progress: - Parallelizing page freeing in the exit/munmap paths - CPU hotplug support The core ktask code is based on work by Pavel Tatashin, Steve Sistare, and Jonathan Adams. ktask v1 RFC: https://lkml.org/lkml/2017/7/14/666 ktask v2 RFC: https://lkml.org/lkml/2017/8/24/801 [*] http://ozlabs.org/~akpm/mmots/broken-out/mm-split-deferred_init_range-into-initializing-and-freeing-parts.patch Daniel Jordan (7): ktask: add documentation ktask: multithread CPU-intensive kernel work ktask: add /proc/sys/debug/ktask_max_threads mm: enlarge type of offset argument in mem_map_offset and mem_map_next mm: parallelize clear_gigantic_page hugetlbfs: parallelize hugetlbfs_fallocate with ktask mm: parallelize deferred struct page initialization within each node Documentation/core-api/index.rst | 1 + Documentation/core-api/ktask.rst | 173 ++++++++++++ fs/hugetlbfs/inode.c | 116 ++++++-- include/linux/ktask.h | 255 ++++++++++++++++++ include/linux/ktask_internal.h | 22 ++ include/linux/mm.h | 6 + init/Kconfig | 12 + init/main.c | 2 + kernel/Makefile | 2 +- kernel/ktask.c | 556 +++++++++++++++++++++++++++++++++++++++ kernel/sysctl.c | 10 + mm/internal.h | 7 +- mm/memory.c | 35 ++- mm/page_alloc.c | 78 ++++-- 14 files changed, 1226 insertions(+), 49 deletions(-) create mode 100644 Documentation/core-api/ktask.rst create mode 100644 include/linux/ktask.h create mode 100644 include/linux/ktask_internal.h create mode 100644 kernel/ktask.c -- 2.15.0
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Jordan <daniel.m.jordan@oracle.com> To: linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: aaron.lu@intel.com, akpm@linux-foundation.org, dave.hansen@linux.intel.com, mgorman@techsingularity.net, mhocko@kernel.org, mike.kravetz@oracle.com, pasha.tatashin@oracle.com, steven.sistare@oracle.com, tim.c.chen@intel.com Subject: [RFC PATCH v3 0/7] ktask: multithread CPU-intensive kernel work Date: Tue, 5 Dec 2017 14:52:13 -0500 [thread overview] Message-ID: <20171205195220.28208-1-daniel.m.jordan@oracle.com> (raw) What do people think of the overall design and direction? There's documentation describing the design in the first patch of the series and the second patch has the API in ktask.h. Thanks, Daniel Changelog: v2 -> v3: - Changed cpu to CPU in the ktask Documentation, as suggested by Randy Dunlap - Saved more boot time now that Pavel Tatashin's deferred struct page init patches are in mainline (https://lkml.org/lkml/2017/10/13/692). New performance results in patch 7. - Added resource limits, per-node and system-wide, to maintain efficient concurrency levels (addresses a concern from my Plumbers talk) - ktask no longer allocates memory internally during a task so it can be used in sensitive contexts - Added the option to run work anywhere on the system rather than always confining it to a specific node - Updated Documentation patch with these changes and reworked motivation section v1 -> v2: - Added deferred struct page initialization use case. - Explained the source of the performance improvement from parallelizing clear_gigantic_page (comment from Dave Hansen). - Fixed Documentation and build warnings from CONFIG_KTASK=n kernels. My Linux Plumbers Unconference Talk: https://www.linuxplumbersconf.org/2017/ocw/proposals/4837 (please ignore OpenID's misapprehension that James Bottomley was speaker) ktask is a generic framework for parallelizing CPU-intensive work in the kernel. The intended use is for big machines that can use their CPU power to speed up large tasks that can't otherwise be multithreaded in userland. The API is generic enough to add concurrency to many different kinds of tasks--for example, zeroing a range of pages or evicting a list of inodes--and aims to save its clients the trouble of splitting up the work, choosing the number of threads to use, starting these threads, and load balancing the work between them. This patchset is based on 4.15-rc2 plus one mmots fix[*] and contains three ktask users: - deferred struct page initialization at boot time - clearing gigantic pages - fallocate for HugeTLB pages Work in progress: - Parallelizing page freeing in the exit/munmap paths - CPU hotplug support The core ktask code is based on work by Pavel Tatashin, Steve Sistare, and Jonathan Adams. ktask v1 RFC: https://lkml.org/lkml/2017/7/14/666 ktask v2 RFC: https://lkml.org/lkml/2017/8/24/801 [*] http://ozlabs.org/~akpm/mmots/broken-out/mm-split-deferred_init_range-into-initializing-and-freeing-parts.patch Daniel Jordan (7): ktask: add documentation ktask: multithread CPU-intensive kernel work ktask: add /proc/sys/debug/ktask_max_threads mm: enlarge type of offset argument in mem_map_offset and mem_map_next mm: parallelize clear_gigantic_page hugetlbfs: parallelize hugetlbfs_fallocate with ktask mm: parallelize deferred struct page initialization within each node Documentation/core-api/index.rst | 1 + Documentation/core-api/ktask.rst | 173 ++++++++++++ fs/hugetlbfs/inode.c | 116 ++++++-- include/linux/ktask.h | 255 ++++++++++++++++++ include/linux/ktask_internal.h | 22 ++ include/linux/mm.h | 6 + init/Kconfig | 12 + init/main.c | 2 + kernel/Makefile | 2 +- kernel/ktask.c | 556 +++++++++++++++++++++++++++++++++++++++ kernel/sysctl.c | 10 + mm/internal.h | 7 +- mm/memory.c | 35 ++- mm/page_alloc.c | 78 ++++-- 14 files changed, 1226 insertions(+), 49 deletions(-) create mode 100644 Documentation/core-api/ktask.rst create mode 100644 include/linux/ktask.h create mode 100644 include/linux/ktask_internal.h create mode 100644 kernel/ktask.c -- 2.15.0 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-12-05 19:51 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-05 19:52 Daniel Jordan [this message] 2017-12-05 19:52 ` [RFC PATCH v3 0/7] ktask: multithread CPU-intensive kernel work Daniel Jordan 2017-12-05 19:52 ` [RFC PATCH v3 1/7] ktask: add documentation Daniel Jordan 2017-12-05 19:52 ` Daniel Jordan 2017-12-05 20:59 ` Daniel Jordan 2017-12-05 20:59 ` Daniel Jordan 2017-12-06 14:35 ` Michal Hocko 2017-12-06 14:35 ` Michal Hocko 2017-12-06 20:32 ` Daniel Jordan 2017-12-06 20:32 ` Daniel Jordan 2017-12-08 12:43 ` Michal Hocko 2017-12-08 12:43 ` Michal Hocko 2017-12-08 13:46 ` Daniel Jordan 2017-12-08 13:46 ` Daniel Jordan 2017-12-05 19:52 ` [RFC PATCH v3 2/7] ktask: multithread CPU-intensive kernel work Daniel Jordan 2017-12-05 19:52 ` Daniel Jordan 2017-12-05 22:21 ` Andrew Morton 2017-12-05 22:21 ` Andrew Morton 2017-12-06 14:21 ` Daniel Jordan 2017-12-06 14:21 ` Daniel Jordan 2017-12-05 19:52 ` [RFC PATCH v3 3/7] ktask: add /proc/sys/debug/ktask_max_threads Daniel Jordan 2017-12-05 19:52 ` Daniel Jordan 2017-12-05 19:52 ` [RFC PATCH v3 4/7] mm: enlarge type of offset argument in mem_map_offset and mem_map_next Daniel Jordan 2017-12-05 19:52 ` Daniel Jordan 2017-12-05 19:52 ` [RFC PATCH v3 5/7] mm: parallelize clear_gigantic_page Daniel Jordan 2017-12-05 19:52 ` Daniel Jordan 2017-12-05 19:52 ` [RFC PATCH v3 6/7] hugetlbfs: parallelize hugetlbfs_fallocate with ktask Daniel Jordan 2017-12-05 19:52 ` Daniel Jordan 2017-12-05 19:52 ` [RFC PATCH v3 7/7] mm: parallelize deferred struct page initialization within each node Daniel Jordan 2017-12-05 19:52 ` Daniel Jordan 2017-12-05 22:23 ` [RFC PATCH v3 0/7] ktask: multithread CPU-intensive kernel work Andrew Morton 2017-12-05 22:23 ` Andrew Morton 2017-12-06 14:21 ` Daniel Jordan 2017-12-06 14:21 ` Daniel Jordan
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=20171205195220.28208-1-daniel.m.jordan@oracle.com \ --to=daniel.m.jordan@oracle.com \ --cc=aaron.lu@intel.com \ --cc=akpm@linux-foundation.org \ --cc=dave.hansen@linux.intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mgorman@techsingularity.net \ --cc=mhocko@kernel.org \ --cc=mike.kravetz@oracle.com \ --cc=pasha.tatashin@oracle.com \ --cc=steven.sistare@oracle.com \ --cc=tim.c.chen@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.