From: Xuekun Hu <xuekun.hu@gmail.com>
To: linux-btrace@vger.kernel.org
Subject: Re: accuracy of btt result on btreplay?
Date: Mon, 08 Mar 2010 08:38:33 +0000 [thread overview]
Message-ID: <398d69301003080038m705acfdbv3193eb5576bb2f92@mail.gmail.com> (raw)
In-Reply-To: <398d69301003022341r5840a9e1g492c243c330bd398@mail.gmail.com>
I think I found where the "S" flag was put for write IO request. In
the kernel function __blockdev_direct_IO(), every write request will
be tagged as "sync". Since btreplay uses O_DIRECT + AIO, which should
go into __blockdev_direct_IO.
So now my views on btreplay:
1. for write request, btreplay will decrease merge rates, thus impact
the latency etc.
2. for read request, btrecord may adjust "-max-pkts"/"-max-bunch-time"
to control the size of bunch to close to the real read IO merge rates.
Thx, Xuekun
On Fri, Mar 5, 2010 at 3:30 PM, Xuekun Hu <xuekun.hu@gmail.com> wrote:
> Updates. I decreased/increased max-pkts to 1/16, however nothing
> changed, still less merges in the replay run.
>
> I think the "S" attribute for "write" should be the reason. First I
> suspected the "S" attribute is brought by io_submit system call,
> however I tested aio-stress tool which uses io_submit to send AIO
> also. In the gathering traces, the write operations doesn't have "S"
> attribute, however during replay, the "S" attribute happened again.
>
> So I wonder where the "S" comes from? Does anyone have suggestions?
> Thanks in advance.
>
> Thx, Xuekun
>
prev parent reply other threads:[~2010-03-08 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 7:41 accuracy of btt result on btreplay? Xuekun Hu
2010-03-03 14:05 ` Alan D. Brunelle
2010-03-04 1:37 ` Xuekun Hu
2010-03-05 7:30 ` Xuekun Hu
2010-03-08 8:38 ` Xuekun Hu [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=398d69301003080038m705acfdbv3193eb5576bb2f92@mail.gmail.com \
--to=xuekun.hu@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