From: "Christian Kujau" <lists@nerdbynature.de>
To: "Dave Kleikamp" <shaggy@linux.vnet.ibm.com>
Cc: "David Fix" <davidf@mrxfx.com>,
"JFS Discussion" <jfs-discussion@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [Jfs-discussion] Hello and a question about high cpu usage on jfsCommit (kernel 2.6.25.1)
Date: Tue, 20 May 2008 14:19:17 +0200 (CEST) [thread overview]
Message-ID: <36b30e3d53d743626dc8cbc080f928c1.squirrel@housecafe.dyndns.org> (raw)
In-Reply-To: <1211211433.6283.14.camel@norville.austin.ibm.com>
On Mon, May 19, 2008 17:37, Dave Kleikamp wrote:
>> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
>> 2669 root 15 -5 0 0 0 R 99 0.0 19:45.71 jfsCommit
>>
> This is highly unusual. Is this thread continually eating cpu at this
> rate, or does it happen in spurts?
Would oprofile[0] help to see what jfsCommit is doing here?
C.
[0] http://oprofile.sf.net
--
make bzImage, not war
next prev parent reply other threads:[~2008-05-20 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 19:35 David Fix
2008-05-15 20:15 ` David Fix
2008-05-19 15:37 ` Dave Kleikamp
2008-05-20 12:19 ` Christian Kujau [this message]
2008-05-20 13:06 ` David Fix
2008-05-20 14:10 ` Dave Kleikamp
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=36b30e3d53d743626dc8cbc080f928c1.squirrel@housecafe.dyndns.org \
--to=lists@nerdbynature.de \
--cc=davidf@mrxfx.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.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
all inboxes | Powered by JetHome®