From: Andi Kleen <andi@firstfloor.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-mm@kvack.org, xfs@oss.sgi.com,
"Ryan C. England" <ryan.england@corvidtec.com>
Subject: Re: XFS causing stack overflow
Date: Fri, 09 Dec 2011 11:53:36 -0800 [thread overview]
Message-ID: <m2aa71plmn.fsf@firstfloor.org> (raw)
In-Reply-To: <20111209115513.GA19994__23079.9863501035$1323435203$gmane$org@infradead.org> (Christoph Hellwig's message of "Fri, 9 Dec 2011 06:55:13 -0500")
Christoph Hellwig <hch@infradead.org> writes:
>
> You probably have only a third of the stack actually used by XFS, the
> rest is from NFSD/writeback code and page reclaim. I don't think any
> of this is easily fixable in a 2.6.32 codebase. Current mainline 3.2-rc
> now has the I/O-less balance dirty pages which will basically split the
> stack footprint in half, but it's an invasive change to the writeback
> code that isn't easily backportable.
An easy fix would be 16k stacks. Don't think they're that difficult
to do, but would need a special binary.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Ryan C. England" <ryan.england@corvidtec.com>,
linux-mm@kvack.org, xfs@oss.sgi.com
Subject: Re: XFS causing stack overflow
Date: Fri, 09 Dec 2011 11:53:36 -0800 [thread overview]
Message-ID: <m2aa71plmn.fsf@firstfloor.org> (raw)
In-Reply-To: <20111209115513.GA19994__23079.9863501035$1323435203$gmane$org@infradead.org> (Christoph Hellwig's message of "Fri, 9 Dec 2011 06:55:13 -0500")
Christoph Hellwig <hch@infradead.org> writes:
>
> You probably have only a third of the stack actually used by XFS, the
> rest is from NFSD/writeback code and page reclaim. I don't think any
> of this is easily fixable in a 2.6.32 codebase. Current mainline 3.2-rc
> now has the I/O-less balance dirty pages which will basically split the
> stack footprint in half, but it's an invasive change to the writeback
> code that isn't easily backportable.
An easy fix would be 16k stacks. Don't think they're that difficult
to do, but would need a special binary.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-12-09 19:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 18:03 XFS causing stack overflow Ryan C. England
2011-12-09 11:55 ` Christoph Hellwig
2011-12-09 11:55 ` Christoph Hellwig
2011-12-09 15:56 ` Ryan C. England
2011-12-09 15:56 ` Ryan C. England
2011-12-09 22:19 ` Dave Chinner
2011-12-09 22:19 ` Dave Chinner
[not found] ` <20111209221956.GE14273__25752.826271537$1323469420$gmane$org@dastard>
2011-12-10 19:52 ` Andi Kleen
2011-12-10 19:52 ` Andi Kleen
2011-12-10 22:13 ` Dave Chinner
2011-12-10 22:13 ` Dave Chinner
2011-12-11 0:00 ` Andi Kleen
2011-12-11 0:00 ` Andi Kleen
2011-12-11 23:05 ` Dave Chinner
2011-12-11 23:05 ` Dave Chinner
2011-12-12 2:31 ` Andi Kleen
2011-12-12 2:31 ` Andi Kleen
2011-12-12 4:36 ` Dave Chinner
2011-12-12 4:36 ` Dave Chinner
2011-12-12 5:13 ` Andi Kleen
2011-12-12 5:13 ` Andi Kleen
2011-12-12 9:00 ` Dave Chinner
2011-12-12 9:00 ` Dave Chinner
2011-12-12 13:43 ` Ryan C. England
2011-12-12 13:43 ` Ryan C. England
2011-12-12 22:47 ` Dave Chinner
2011-12-12 22:47 ` Dave Chinner
[not found] ` <20111209115513.GA19994__23079.9863501035$1323435203$gmane$org@infradead.org>
2011-12-09 19:53 ` Andi Kleen [this message]
2011-12-09 19:53 ` Andi Kleen
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=m2aa71plmn.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=ryan.england@corvidtec.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.