linux-btrace.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: Re: lots of unplugged by timer normal or abnormal?
Date: Tue, 06 Oct 2009 19:50:45 +0000	[thread overview]
Message-ID: <1254858645.4852.87.camel@cail> (raw)
In-Reply-To: <20091006185337.GF26949@hostway.ca>

On Tue, 2009-10-06 at 11:53 -0700, Simon Kirby wrote:
> Hello,
> 
> I was just testing out blktrace/blkparse/btrace on a box that is hitting
> some performance walls, and noticed that there are a fair amonut of "UT"
> events (unplug by timer).  Is this normal/expected?  For example:
> 
> [sroot@nas04:/root]# btrace /dev/etherd/e7.0 | grep T
> 152,32   4     1379     3.582513494     0 UT   N [swapper] 8
> 152,32   1     1289     4.329760067     0 UT   N [swapper] 1
> 152,32   3     1132     4.362257911     0 UT   N [swapper] 3
> 152,32   7     1070     4.375258374     0 UT   N [swapper] 1
> 152,32   3     1146     4.382260172     0 UT   N [swapper] 5
> 152,32   1     1318     4.417759727  2830 UT   N [nfsd] 3
> 152,32   5     1003     4.498757105     0 UT   N [swapper] 1
> 152,32   1     1368     4.517761127     0 UT   N [swapper] 1
> 152,32   0     1133     4.585522116     0 UT   N [swapper] 5
> 
> This is on 2.6.30.5 with the 2.6.30.6 XFS patches.
> 
> Cheers,
> 
> Simon-

Hello Simon- 

This looks pretty bad - could you tell me what distro you are running on
as a base? And did this happen before 2.6.30.5 (the poor performance)?
And could you provide a more complete snippet of blktrace output
(showing a handful of complete ops)?

Thanks,
Alan D. Brunelle
Hewlett-Packard


  reply	other threads:[~2009-10-06 19:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 18:53 lots of unplugged by timer normal or abnormal? Simon Kirby
2009-10-06 19:50 ` Alan D. Brunelle [this message]
2009-10-06 20:08 ` Simon Kirby
2009-10-06 20:20 ` Alan D. Brunelle
2009-10-11 16:44 ` Simon Kirby
2009-10-11 18:35 ` Jens Axboe
2009-10-11 20:58 ` Simon Kirby
2009-10-12  7:18 ` Jens Axboe

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=1254858645.4852.87.camel@cail \
    --to=alan.brunelle@hp.com \
    --cc=linux-btrace@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).