From: "Måns Rullgård" <mans@mansr.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
Tim Bird <tim.bird@am.sony.com>, Joe Perches <joe@perches.com>,
linux kernel <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
Russell King <rmk@arm.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/3] ARM 4Kstacks: introduction
Date: Sat, 22 Oct 2011 14:13:55 +0100 [thread overview]
Message-ID: <yw1x1uu5p3sc.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <CACVXFVMb9p8PiTYWGTNn-FtQts0sRgmK+BQ6kaJ6-D89CAT=xQ@mail.gmail.com> (Ming Lei's message of "Sat, 22 Oct 2011 16:50:15 +0800")
Ming Lei <tom.leiming@gmail.com> writes:
> On Wed, Oct 19, 2011 at 6:51 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Tuesday 18 October 2011 17:26:44 Tim Bird wrote:
>>> Even inside Sony, usage of 4K stacks is limited
>>> to some very special cases, where memory is exceedingly
>>> tight (we have one system with 4M of RAM). And we
>>> don't mind lopping off features or coding around
>>> problem areas to support our special case.
>>
>> I would imagine that in those cases, you can gain more by reducing the
>> number of threads in the system. What is the highest number of
>> concurrent threads that you expect in a limited use case with no
>> networking or block devices?
>
> If system run for some time, sometimes it may be difficult for
> memory allocator to allocate 2 continuous page frames even there are
> many spare page frames in system because of
> fragment issue, so the patch does make sense. Anyway,
> it provides one option for user to apply 4k stack to avoid
> such kind of process creation failure.
Can't page migration be used in these situations?
--
Måns Rullgård
mans@mansr.com
next prev parent reply other threads:[~2011-10-22 13:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 23:27 Tim Bird
2011-10-18 23:29 ` [PATCH 1/3] ARM 4Kstacks: Add support for 4K kernel stacks to ARM Tim Bird
2011-10-18 23:31 ` [PATCH 2/3] ARM: Add static kernel function stack size analyzer, for ARM Tim Bird
2011-10-19 10:45 ` Arnd Bergmann
2011-10-21 17:03 ` Andi Kleen
2011-10-18 23:34 ` [PATCH 3/3] ARM 4Kstacks: Decrease poll and select stack usage, when using 4K stacks Tim Bird
2011-10-20 12:21 ` Arnd Bergmann
2011-10-19 0:14 ` [PATCH 0/3] ARM 4Kstacks: introduction Joe Perches
2011-10-19 0:26 ` Tim Bird
2011-10-19 0:31 ` Joe Perches
2011-10-19 23:43 ` Tim Bird
2011-10-19 4:54 ` Dave Chinner
2011-10-19 5:02 ` Andi Kleen
2011-10-19 10:51 ` Arnd Bergmann
2011-10-22 8:50 ` Ming Lei
2011-10-22 13:13 ` Måns Rullgård [this message]
2011-10-22 14:27 ` Andi Kleen
2011-10-22 13:36 ` Russell King - ARM Linux
2011-10-23 19:25 ` Tim Bird
2011-10-23 20:11 ` Russell King - ARM Linux
2011-10-24 10:36 ` Ming Lei
2011-10-23 14:06 ` Bernd Petrovitsch
2011-10-19 4:33 ` Dave Chinner
2011-10-19 7:35 ` Russell King - ARM Linux
2011-10-19 23:36 ` Tim Bird
2011-10-20 0:13 ` Måns Rullgård
2011-10-20 1:08 ` Tim Bird
2011-10-20 1:55 ` Måns Rullgård
2011-10-20 22:21 ` Dave Chinner
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=yw1x1uu5p3sc.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=andi@firstfloor.org \
--cc=arnd@arndb.de \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.com \
--cc=tom.leiming@gmail.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
all inboxes | Powered by JetHome®