public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Dave Hall <kdhall@binghamton.edu>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs_fsr, sunit, and swidth
Date: Thu, 28 Mar 2013 12:38:41 +1100	[thread overview]
Message-ID: <20130328013841.GB6369@dastard> (raw)
In-Reply-To: <515082C3.2000006@binghamton.edu>

On Mon, Mar 25, 2013 at 01:00:51PM -0400, Dave Hall wrote:
> 
> Dave Hall
> Binghamton University
> kdhall@binghamton.edu
> 607-760-2328 (Cell)
> 607-777-4641 (Office)
> 
> 
> On 03/16/2013 03:21 AM, Dave Chinner wrote:
> >Using perf to profile the kernel while the cp -al workload is
> >running will tell use exactly where the CPU is being burnt. That
> >will confirm the analysis, or point us at some other issue that is
> >causing excessive CPU burn...
> >
> Dave,  which perf command(s) would you like me to run.  (I'm
> familiar with the concept behind this kind of tool, but I haven't
> worked with this one before).

Just run 'perf top -U' for 10s while the problem is occurring and
pastebin the output....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2013-03-28  1:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 18:11 xfs_fsr, sunit, and swidth Dave Hall
2013-03-13 23:57 ` Dave Chinner
2013-03-14  0:03 ` Stan Hoeppner
     [not found]   ` <514153ED.3000405@binghamton.edu>
2013-03-14 12:26     ` Stan Hoeppner
2013-03-14 12:55       ` Stan Hoeppner
2013-03-14 14:59         ` Dave Hall
2013-03-14 18:07           ` Stefan Ring
2013-03-15  5:14           ` Stan Hoeppner
2013-03-15 11:45             ` Dave Chinner
2013-03-16  4:47               ` Stan Hoeppner
2013-03-16  7:21                 ` Dave Chinner
2013-03-16 11:45                   ` Stan Hoeppner
2013-03-25 17:00                   ` Dave Hall
2013-03-27 21:16                     ` Stan Hoeppner
2013-03-29 19:59                       ` Dave Hall
2013-03-31  1:22                         ` Dave Chinner
2013-04-02 10:34                           ` Hans-Peter Jansen
2013-04-03 14:25                           ` Dave Hall
2013-04-12 17:25                             ` Dave Hall
2013-04-13  0:45                               ` Dave Chinner
2013-04-13  0:51                               ` Stan Hoeppner
2013-04-15 20:35                                 ` Dave Hall
2013-04-16  1:45                                   ` Stan Hoeppner
2013-04-16 16:18                                   ` Dave Chinner
2015-02-22 23:35                                     ` XFS/LVM/Multipath on a single RAID volume Dave Hall
2015-02-23 11:18                                       ` Emmanuel Florac
2015-02-24 22:04                                         ` Dave Hall
2015-02-24 22:33                                           ` Dave Chinner
     [not found]                                             ` <54ED01BC.6080302@binghamton.edu>
2015-02-24 23:33                                               ` Dave Chinner
2015-02-25 11:49                                             ` Emmanuel Florac
2015-02-25 11:21                                           ` Emmanuel Florac
2013-03-28  1:38                     ` Dave Chinner [this message]

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=20130328013841.GB6369@dastard \
    --to=david@fromorbit.com \
    --cc=kdhall@binghamton.edu \
    --cc=xfs@oss.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