From: yalin.wang2010@gmail.com (yalin wang)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator
Date: Tue, 26 May 2015 10:52:43 +0800 [thread overview]
Message-ID: <CAFP4FLr3gwnwg--tqJVFemPyKX=cmdakYJBeJ5BqvZeoBd2zbQ@mail.gmail.com> (raw)
In-Reply-To: <1432483340-23157-1-git-send-email-jungseoklee85@gmail.com>
2015-05-25 0:02 GMT+08:00 Jungseok Lee <jungseoklee85@gmail.com>:
> Fork-routine sometimes fails to get a physically contiguous region for
> thread_info on 4KB page system although free memory is enough. That is,
> a physically contiguous region, which is currently 16KB, is not available
> since system memory is fragmented.
>
> This patch tries to solve the problem as allocating thread_info memory
> from vmalloc space, not 1:1 mapping one. The downside is one additional
> page allocation in case of vmalloc. However, vmalloc space is large enough,
> around 240GB, under a combination of 39-bit VA and 4KB page. Thus, it is
> not a big tradeoff for fork-routine service.
>
> Suggested-by: Sungjinn Chung <barami97@gmail.com>
> Signed-off-by: Jungseok Lee <jungseoklee85@gmail.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: linux-kernel at vger.kernel.org
> Cc: linux-mm at kvack.org
> ---
> arch/arm64/Kconfig | 12 ++++++++++++
> arch/arm64/include/asm/thread_info.h | 9 +++++++++
> arch/arm64/kernel/process.c | 7 +++++++
> 3 files changed, 28 insertions(+)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 99930cf..93c236a 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -536,6 +536,18 @@ config ARCH_SELECT_MEMORY_MODEL
> config HAVE_ARCH_PFN_VALID
> def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
>
> +config ARCH_THREAD_INFO_ALLOCATOR
> + bool "Enable vmalloc based thread_info allocator (EXPERIMENTAL)"
> + depends on ARM64_4K_PAGES
> + default n
> + help
> + This feature enables vmalloc based thread_info allocator. It
> + prevents fork-routine from begin failed to obtain physically
> + contiguour region due to memory fragmentation on low system
> + memory platforms.
> +
> + If unsure, say N
> +
> config HW_PERF_EVENTS
> bool "Enable hardware performance counter support for perf events"
> depends on PERF_EVENTS
> diff --git a/arch/arm64/include/asm/thread_info.h b/arch/arm64/include/asm/thread_info.h
> index dcd06d1..e753e59 100644
> --- a/arch/arm64/include/asm/thread_info.h
> +++ b/arch/arm64/include/asm/thread_info.h
> @@ -61,6 +61,15 @@ struct thread_info {
> #define init_thread_info (init_thread_union.thread_info)
> #define init_stack (init_thread_union.stack)
>
> +#ifdef CONFIG_ARCH_THREAD_INFO_ALLOCATOR
> +#define alloc_thread_info_node(tsk, node) \
> +({ \
> + __vmalloc_node_range(THREAD_SIZE, THREAD_SIZE, VMALLOC_START, \
> + VMALLOC_END, GFP_KERNEL, PAGE_KERNEL, 0, \
> + NUMA_NO_NODE, __builtin_return_address(0)); \
> +})
why not add __GFP_HIGHMEM, if you decided to use vmalloc() alloc stack pages?
Thanks
next prev parent reply other threads:[~2015-05-26 2:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 16:02 [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator Jungseok Lee
2015-05-24 17:49 ` Arnd Bergmann
2015-05-25 10:01 ` Jungseok Lee
2015-05-25 14:58 ` Minchan Kim
2015-05-26 12:10 ` Jungseok Lee
2015-05-27 4:24 ` Minchan Kim
2015-05-27 16:00 ` Jungseok Lee
2015-05-25 16:47 ` Catalin Marinas
2015-05-25 20:29 ` Arnd Bergmann
2015-05-25 22:36 ` Catalin Marinas
2015-05-26 9:51 ` Arnd Bergmann
2015-05-26 13:02 ` Jungseok Lee
2015-05-25 21:20 ` Arnd Bergmann
2015-05-25 14:40 ` Minchan Kim
2015-05-26 11:29 ` Jungseok Lee
2015-05-27 4:10 ` Minchan Kim
2015-05-27 6:22 ` Sergey Senozhatsky
2015-05-27 7:31 ` Arnd Bergmann
2015-05-27 16:05 ` Jungseok Lee
2015-05-27 16:08 ` Jungseok Lee
2015-05-26 2:52 ` yalin wang [this message]
2015-05-26 12:21 ` Jungseok Lee
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='CAFP4FLr3gwnwg--tqJVFemPyKX=cmdakYJBeJ5BqvZeoBd2zbQ@mail.gmail.com' \
--to=yalin.wang2010@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).