From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Paul Jackson <pj@sgi.com>
Cc: Zhao Forrest <forrest.zhao@gmail.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:06:16 +0200 [thread overview]
Message-ID: <1176285976.6893.27.camel@twins> (raw)
In-Reply-To: <20070411025305.b9131062.pj@sgi.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Paul Jackson <pj@sgi.com>
Cc: Zhao Forrest <forrest.zhao@gmail.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:06:16 +0200 [thread overview]
Message-ID: <1176285976.6893.27.camel@twins> (raw)
In-Reply-To: <20070411025305.b9131062.pj@sgi.com>
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.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-04-11 10:06 UTC|newest]
Thread overview: 35+ 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:17 ` Zhao Forrest
2007-04-11 6:53 ` Pekka Enberg
2007-04-11 6:53 ` Pekka Enberg
2007-04-11 9:14 ` Zhao Forrest
2007-04-11 9:14 ` Zhao Forrest
2007-04-11 9:53 ` Paul Jackson
2007-04-11 9:53 ` Paul Jackson
2007-04-11 10:06 ` Peter Zijlstra [this message]
2007-04-11 10:06 ` Peter Zijlstra
2007-04-11 10:10 ` Zhao Forrest
2007-04-11 10:10 ` Zhao Forrest
2007-04-11 10:16 ` Peter Zijlstra
2007-04-11 10:16 ` Peter Zijlstra
2007-04-11 16:23 ` Chuck Ebbert
2007-04-11 16:23 ` Chuck Ebbert
2007-04-11 16:44 ` Badari Pulavarty
2007-04-11 16:44 ` Badari Pulavarty
2007-04-11 9:53 ` Zhao Forrest
2007-04-11 9:53 ` Zhao Forrest
2007-04-11 10:38 ` Peter Zijlstra
2007-04-11 10:38 ` Peter Zijlstra
2007-04-11 16:35 ` Ken Chen
2007-04-11 16:35 ` Ken Chen
2007-04-12 6:17 ` Zhao Forrest
2007-04-12 6:17 ` Zhao Forrest
2007-04-11 22:30 ` Andrew Morton
2007-04-11 22:30 ` Andrew Morton
2007-04-12 7:39 ` Peter Zijlstra
2007-04-12 7:39 ` Peter Zijlstra
2007-04-12 7:55 ` Andrew Morton
2007-04-12 7:55 ` Andrew Morton
2007-04-12 9:19 ` Peter Zijlstra
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=1176285976.6893.27.camel@twins \
--to=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 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.