From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-32: remove CONFIG_4KSTACKS
Date: Wed, 16 Jun 2010 11:21:36 +0100 [thread overview]
Message-ID: <20100616112136.42ab08ef@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20100616091621.GA4486@lst.de>
On Wed, 16 Jun 2010 11:16:21 +0200
Christoph Hellwig <hch@lst.de> wrote:
> These days 4 kilobytes of stack just aren't enough for reliably operation,
> and people using lots of threads have long switched to x86-64, so remove the
> CONFIG_4KSTACKS option.
It's very useful for things like debugging and because of the split
kernel/irq stacks. It also seems to be quite adequate for most
configurations.
Perhaps XFS should select 8K stack instead ?
next prev parent reply other threads:[~2010-06-16 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 9:16 Christoph Hellwig
2010-06-16 10:21 ` Alan Cox [this message]
2010-06-16 10:20 ` Christoph Hellwig
2010-06-16 10:23 ` Kyle McMartin
2010-06-16 10:46 ` Milan Broz
2010-06-16 10:49 ` Kyle McMartin
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=20100616112136.42ab08ef@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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
Powered by JetHome