From: Ted Ts'o <tytso@mit.edu>
To: Sean McCauliff <Sean.D.McCauliff@nasa.gov>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: High CPU Utilization When Copying to Ext4
Date: Wed, 29 Jun 2011 22:33:06 -0400 [thread overview]
Message-ID: <20110630023306.GY2729@thunk.org> (raw)
In-Reply-To: <4E0BBCE9.9020600@nasa.gov>
On Wed, Jun 29, 2011 at 05:01:45PM -0700, Sean McCauliff wrote:
> Sorry, I didn't mean to bother you. I did try and email ext3-users
> so as to not take up any developer time with my question.
Yeah, but it's not likely anyone on that list would be able to help
you. Both ext3 and ext4 isn't expected to take a huge amount of CPU
under normal conditions when doing this type of copying where you will
be likely disk bound.
Well, you're not using fallocate() (at least you haven't disclosed it
to date), and writing into fallocated space is the only thing that
would be using a workqueue at all (which is what the kworker threads
are using).
So I very much doubt it has anything to do with ext4. The fiber
channel drivers do use workqueues a fair amount, so yes, it would be
useful to know that you are using a fiber channel SAN. At this point
I'd suggest that you use oprofile or perf to see where the CPU is
being consumed. Perf is probably better since it will allow you to
see the call chains.
- Ted
next prev parent reply other threads:[~2011-06-30 2:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <341DAA96EE3A8444B6E4657BE8A846EA4B3DA126FE@NDJSSCC06.ndc.nasa.gov>
2011-06-27 3:05 ` High CPU Utilization When Copying to Ext4 Ted Ts'o
2011-06-27 9:24 ` Lukas Czerner
2011-06-28 18:37 ` Mccauliff, Sean D. (ARC-PX)[Lockheed Martin Space OPNS]
2011-06-28 20:14 ` Theodore Tso
2011-06-28 20:20 ` Mccauliff, Sean D. (ARC-PX)[Lockheed Martin Space OPNS]
2011-06-29 13:08 ` Theodore Tso
2011-06-30 0:01 ` Sean McCauliff
2011-06-30 2:33 ` Ted Ts'o [this message]
2011-07-08 17:08 ` Sean McCauliff
2011-07-08 17:17 ` Andi Kleen
2011-07-08 17:41 ` Sean McCauliff
2011-07-08 18:24 ` Ted Ts'o
2011-06-28 20:17 ` Andreas Dilger
2011-06-29 23:16 ` Sean McCauliff
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=20110630023306.GY2729@thunk.org \
--to=tytso@mit.edu \
--cc=Sean.D.McCauliff@nasa.gov \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).