From: Andi Kleen <andi@firstfloor.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Adrian Bunk <bunk@kernel.org>,
Oliver Pinter <oliver.pntr@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@infradead.org>,
David Chinner <dgc@sgi.com>,
xfs@oss.sgi.com
Subject: Re: x86: 4kstacks default
Date: Sun, 20 Apr 2008 13:48:40 +0200 [thread overview]
Message-ID: <87abjobvc7.fsf@basil.nowhere.org> (raw)
In-Reply-To: <480AA2B9.10305__23983.3358479247$1208657639$gmane$org@sandeen.net> (Eric Sandeen's message of "Sat, 19 Apr 2008 20:56:09 -0500")
Eric Sandeen <sandeen@sandeen.net> writes:
> Adrian Bunk wrote:
>> On Sat, Apr 19, 2008 at 04:35:31PM +0200, Oliver Pinter wrote:
>>> ...
>>> with the older kernel is typical: xfs+nfs+4k stack(+lvm)
>>
>> Does anyone still experience problems with 2.6.25?
>
> There are always problems. You can always come up with something that
> will crash in 4k, IMHO.
But what are a few crashes compared against the ability to run 50000
kernel threads on a 32bit machine? Something has to give in the aim
for useless checkbox numbers after all.
-Andi
prev parent reply other threads:[~2008-04-20 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804181737.m3IHbabI010051@hera.kernel.org>
[not found] ` <20080418142934.38ce6bf4.akpm@linux-foundation.org>
[not found] ` <20080419142329.GA5339@elte.hu>
2008-04-19 14:35 ` x86: 4kstacks default Oliver Pinter
2008-04-19 15:19 ` Adrian Bunk
2008-04-19 15:42 ` Oliver Pinter
2008-04-20 1:56 ` Eric Sandeen
2008-04-20 7:42 ` Adrian Bunk
2008-04-20 16:59 ` Chris Wedgwood
[not found] ` <480AA2B9.10305__23983.3358479247$1208657639$gmane$org@sandeen.net>
2008-04-20 11:48 ` Andi Kleen [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=87abjobvc7.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=bunk@kernel.org \
--cc=dgc@sgi.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oliver.pntr@gmail.com \
--cc=sandeen@sandeen.net \
--cc=tglx@linutronix.de \
--cc=xfs@oss.sgi.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