From: david@fromorbit.com (Dave Chinner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM 4Kstacks: introduction
Date: Fri, 21 Oct 2011 09:21:09 +1100 [thread overview]
Message-ID: <20111020222109.GB14993@dastard> (raw)
In-Reply-To: <4E9F5F1B.1020106@am.sony.com>
On Wed, Oct 19, 2011 at 04:36:59PM -0700, Tim Bird wrote:
> On 10/19/2011 12:35 AM, Russell King - ARM Linux wrote:
> > On Tue, Oct 18, 2011 at 04:27:45PM -0700, Tim Bird wrote:
> >> I'm about to submit a set of patches (really pretty small)
> >> to add 4K stack support to ARM (defaulted to 'N').
> >>
> >> This has been kicking around in my Sony tree for a few years,
> >> and it's about time to mainline it. The first patch is
> >> the actual 4KSTACKS patch. See subsequent patches
> >> for tools to help with stack reduction to avoid the problems
> >> that apparently led to the removal of this feature on x86.
> >
> > This isn't a good idea - if the feature has been abandoned on x86,
> > people aren't going to be soo concerned about the stack usage of
> > each function. They're going to accept that there's more stack
> > space available, and we'll see code paths that start expecting that.
>
> Well, the difference in size is not an order of magnitude. Current
> stacks are only twice as big as what this feature optionally allows.
> So people really shouldn't go crazy with their stack usage.
>
> Granted we're already seeing a bit of stack bloat, but IMHO this should
> be nipped in the bud. If the stack grows a lot more, it will likely
> need to shift to 16K, which would REALLY be costly on machines
> with lots of threads and low memory.
FWIW, I was seriously considering bringing up 16k stacks on x86-64
as a topic for the kernel summit. We've been getting reports of the
8k stack being blown on different filesystems for the past year or
so on relatively trivial storage configs....
Cheers,
Dave.
--
Dave Chinner
david at fromorbit.com
prev parent reply other threads:[~2011-10-20 22:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 23:27 [PATCH 0/3] ARM 4Kstacks: introduction 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
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 [this message]
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=20111020222109.GB14993@dastard \
--to=david@fromorbit.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