Linux btrace development
 help / color / mirror / Atom feed
From: Ming Zhang <blackmagic02881@gmail.com>
To: linux-btrace@vger.kernel.org
Subject: Re: how to understand the Q2Q in btt result?
Date: Mon, 26 Mar 2007 13:30:40 +0000	[thread overview]
Message-ID: <1174915840.3667.4.camel@dhcp-119.ibrix.com> (raw)
In-Reply-To: <1174876819.6887.2.camel@localhost.localdomain>

On Sun, 2007-03-25 at 23:51 -0400, Alan D. Brunelle wrote:
> Ming Zhang wrote:
> > from btt user guide
> >
> > "Q2Q which measures the time between queue traces in the system.
> > This provides some idea as to how quickly IOs are being handed to
> > the block IO layer."
> >
> > does this mean the time between queuing N request and N
> > +1 request?
> >   
> 
> Hi Ming -
> 
> This is the average time between the Q traces being logged. We take the 
> difference between each succeeding Q trace, and divide the sum by the total.

so like block layer idle indicator. maybe a similar D2D will be a nice
device indicator as well.


> 
> Alan
> > thanks!
> >
> > Ming
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-btrace" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >   
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-btrace" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2007-03-26 13:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26  2:40 how to understand the Q2Q in btt result? Ming Zhang
2007-03-26  3:51 ` Alan D. Brunelle
2007-03-26 13:30 ` Ming Zhang [this message]
2007-03-26 13:58 ` Alan D. Brunelle
2007-03-26 15:00 ` Ming Zhang
2007-03-26 15:09 ` Alan D. Brunelle
2007-03-26 15:21 ` Ming Zhang

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=1174915840.3667.4.camel@dhcp-119.ibrix.com \
    --to=blackmagic02881@gmail.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