| To: | Dave Hall <kdhall@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_fsr, sunit, and swidth |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Thu, 28 Mar 2013 12:38:41 +1100 |
| Cc: | "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <515082C3.2000006@xxxxxxxxxxxxxx> |
| References: | <514113C6.9090602@xxxxxxxxxxxxxxxxx> <514153ED.3000405@xxxxxxxxxxxxxx> <5141C1FC.4060209@xxxxxxxxxxxxxxxxx> <5141C8C1.2080903@xxxxxxxxxxxxxxxxx> <5141E5CF.10101@xxxxxxxxxxxxxx> <5142AE40.6040408@xxxxxxxxxxxxxxxxx> <20130315114538.GF6369@dastard> <5143F94C.1020708@xxxxxxxxxxxxxxxxx> <20130316072126.GG6369@dastard> <515082C3.2000006@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Mon, Mar 25, 2013 at 01:00:51PM -0400, Dave Hall wrote: > > Dave Hall > Binghamton University > kdhall@xxxxxxxxxxxxxx > 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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 21/21] xfs: add CRC checks to the superblock, Dave Chinner |
|---|---|
| Next by Date: | oops from deliberate block trashing (of course!), Michael L. Semon |
| Previous by Thread: | Re: xfs_fsr, sunit, and swidth, Dave Chinner |
| Next by Thread: | [PATCH 00/14] xfs: Support for interacting with multiple user namespaces, Eric W. Biederman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |