All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 8 Jul 2011 14:24:25 -0400	[thread overview]
Message-ID: <20110708182425.GC3331@thunk.org> (raw)
In-Reply-To: <4E17398F.2090609@nasa.gov>

OK, #1, can you try doing an experiment with "cp -r <src-path>
<dest-path>", and tell me whether the copy speed is faster or slower,
and whether the CPU utilization is faster or slower?  Even if it's a
bit slower to use cp -r, it will be easier for us to try to reproduce
things and to understand what cp -r is doing as opposed to some
mystery java program.

#2, if you know how to set up ftrace, can you enable the
ext4_mballoc_alloc tracepoint and send me a sample output (a few
hundred lines will be plenty).

The short version is basically:

<start your java copy program>
echo 1 > /sys/kernel/debug/tracing/events/ext4/ext4_mballoc_alloc/enable
<wait 30 seconds>
cat /sys/kernel/debug/tracing/trace > /var/tmp/trace-save
echo 0 > /sys/kernel/debug/tracing/events/ext4/ext4_mballoc_alloc/enable

						- Ted

  parent reply	other threads:[~2011-07-08 18:24 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
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 [this message]
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=20110708182425.GC3331@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 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.