From: Jungseok Lee <jungseoklee85@gmail.com>
To: Catalin Marinas <catalin.marinas@foss.arm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
"barami97@gmail.com" <barami97@gmail.com>,
Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator
Date: Tue, 26 May 2015 22:02:46 +0900 [thread overview]
Message-ID: <E71E3520-FCE5-4DAE-969D-F59F6A331611@gmail.com> (raw)
In-Reply-To: <F68D2983-226C-4704-A1E0-E79C9425B822@foss.arm.com>
On May 26, 2015, at 1:47 AM, Catalin Marinas wrote:
> On 25 May 2015, at 13:01, Jungseok Lee <jungseoklee85@gmail.com> wrote:
>
>>> Could the stack size be reduced to 8KB perhaps?
>>
>> I guess probably not.
>>
>> A commit, 845ad05e, says that 8KB is not enough to cover SpecWeb benchmark.
>
> We could go back to 8KB stacks if we implement support for separate IRQ
> stack on arm64. It's not too complicated, we would have to use SP0 for (kernel) threads
> and SP1 for IRQ handlers.
Definitely interesting.
It looks like there are two options based on discussion.
1) Reduce the stack size with separate IRQ stack scheme
2) Figure out a generic anti-fragmentation solution
Do I miss anything?
I am still not sure about the first scheme as reviewing Minchan's findings repeatedly,
but I agree that the item should be worked actively.
Best Regards
Jungseok Lee
--
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 prev parent reply other threads:[~2015-05-26 13:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 16:02 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 [this message]
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
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=E71E3520-FCE5-4DAE-969D-F59F6A331611@gmail.com \
--to=jungseoklee85@gmail.com \
--cc=arnd@arndb.de \
--cc=barami97@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=catalin.marinas@foss.arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=will.deacon@arm.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