From: Chuck Ebbert <cebbert@redhat.com>
To: Zhao Forrest <forrest.zhao@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Jackson <pj@sgi.com>,
penberg@cs.helsinki.fi, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: Why kmem_cache_free occupy CPU for more than 10 seconds?
Date: Wed, 11 Apr 2007 12:23:28 -0400 [thread overview]
Message-ID: <461D0B80.2020005@redhat.com> (raw)
In-Reply-To: <ac8af0be0704110310n1f237e2el6f34365c4aaa5969@mail.gmail.com>
Zhao Forrest wrote:
> On 4/11/07, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>> On Wed, 2007-04-11 at 02:53 -0700, Paul Jackson wrote:
>> > I'm confused - which end of ths stack is up?
>> >
>> > cpuset_exit doesn't call do_exit, rather it's the other
>> > way around. But put_files_struct doesn't call do_exit,
>> > rather do_exit calls __exit_files calls put_files_struct.
>>
>> I'm guessing its x86_64 which generates crap traces.
>>
> Yes, it's x86_64. Is there a reliable way to generate stack traces under
> x86_64?
> Can enabling "[ ] Compile the kernel with frame pointers" help?
It will help a little, but not much because the stack backtrace
code ignores the frame pointers. But it will prevent tail calls,
making it somewhat easier to make sense of the data.
This should be a FAQ item somewhere...
next prev parent reply other threads:[~2007-04-11 16:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 6:17 Why kmem_cache_free occupy CPU for more than 10 seconds? Zhao Forrest
2007-04-11 6:53 ` Pekka Enberg
2007-04-11 9:14 ` Zhao Forrest
2007-04-11 9:53 ` Paul Jackson
2007-04-11 10:06 ` Peter Zijlstra
2007-04-11 10:10 ` Zhao Forrest
2007-04-11 10:16 ` Peter Zijlstra
2007-04-11 16:23 ` Chuck Ebbert [this message]
2007-04-11 16:44 ` Badari Pulavarty
2007-04-11 9:53 ` Zhao Forrest
2007-04-11 10:38 ` Peter Zijlstra
2007-04-11 16:35 ` Ken Chen
2007-04-12 6:17 ` Zhao Forrest
2007-04-11 22:30 ` Andrew Morton
2007-04-12 7:39 ` Peter Zijlstra
2007-04-12 7:55 ` Andrew Morton
2007-04-12 9:19 ` Peter Zijlstra
[not found] <fa.jxja7Ze2HZEPZZ5vd0w5eLsKf88@ifi.uio.no>
[not found] ` <fa.RbU8KKG9LmOiypCl0DuBe43HL5c@ifi.uio.no>
[not found] ` <fa.7mgz+w23+bQoEmP17EX7CoXvAKk@ifi.uio.no>
[not found] ` <fa.Iwu0x59X2e1XgdDQWyXObWrcbFY@ifi.uio.no>
[not found] ` <fa.Aj3PE3FoH/kmJ6APQFg2oZN1OFc@ifi.uio.no>
2007-04-13 23:26 ` Robert Hancock
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=461D0B80.2020005@redhat.com \
--to=cebbert@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=forrest.zhao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
--cc=pj@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