From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Oops in pdflush
Date: Sat, 28 Feb 2004 10:20:14 +0000 [thread overview]
Message-ID: <16448.27486.350405.688607@napali.hpl.hp.com> (raw)
In-Reply-To: <je4qtl7u44.fsf@sykes.suse.de>
>>>>> On Sat, 28 Feb 2004 21:00:54 +1100, Keith Owens <kaos@sgi.com> said:
Keith> Without DavidM's patch to add
Keith> ia64_invoke_kernel_thread_helper, pdflush starts with 560
Keith> bytes of stack and 744 bytes of rbs. With
Keith> ia64_invoke_kernel_thread_helper, that reduces to 554 bytes
Keith> of stack and 272 bytes of rbs. Backtrace with
Keith> ia64_invoke_kernel_thread_helper.
Cool. Thanks for reporting that and for providing the stack-dump (thanks
to Andreas, too, of course).
Keith> We need both ia64_invoke_kernel_thread_helper and my patch to pdflush.
Keith> Until all architectures have a kernel_thread helper, nested calls to
Keith> kernel_thread will chew up stack.
Yes, I think so, too. Andrew?
--david
next prev parent reply other threads:[~2004-02-28 10:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 13:34 Oops in pdflush Andreas Schwab
2004-02-20 14:18 ` Keith Owens
2004-02-20 14:52 ` Andreas Schwab
2004-02-20 16:41 ` David Mosberger
2004-02-20 17:11 ` Andreas Schwab
2004-02-20 23:09 ` David Mosberger
2004-02-22 13:58 ` Andreas Schwab
2004-02-22 14:08 ` Keith Owens
2004-02-22 16:52 ` Andreas Schwab
2004-02-24 1:54 ` Grant Grundler
2004-02-27 10:16 ` Andreas Schwab
2004-02-27 13:58 ` Keith Owens
2004-02-28 6:52 ` David Mosberger
2004-02-28 9:39 ` David Mosberger
2004-02-28 9:45 ` Keith Owens
2004-02-28 10:00 ` Keith Owens
2004-02-28 10:20 ` David Mosberger [this message]
2004-02-28 10:23 ` Andrew Morton
2004-02-28 12:00 ` Andrew Morton
2004-02-28 14:47 ` Keith Owens
2004-02-28 14:55 ` Andreas Schwab
2004-02-28 18:26 ` David Mosberger
2004-02-28 23:59 ` Keith Owens
2004-02-29 3:44 ` Keith Owens
2004-02-29 5:27 ` Andrew Morton
2004-03-01 10:34 ` Andreas Schwab
2004-03-01 19:46 ` David Mosberger
2006-09-06 13:39 ` D.N.Jagannathan
2006-09-06 17:44 ` Chen, Kenneth W
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=16448.27486.350405.688607@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.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