From: Ryo Tsuruta <ryov@valinux.co.jp>
To: baramsori72@gmail.com
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
containers@lists.linux-foundation.org,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xensource.com, agk@sourceware.org,
fernando@oss.ntt.co.jp, xemul@openvz.org,
balbir@linux.vnet.ibm.com
Subject: Re: [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.7.0: Introduction
Date: Wed, 08 Oct 2008 19:40:22 +0900 (JST) [thread overview]
Message-ID: <20081008.194022.226783199.ryov@valinux.co.jp> (raw)
In-Reply-To: <2891419e0810080129sb6b35y11362f4bef71c174@mail.gmail.com>
Hi Dong-Jae,
Thanks for being intersted in dm-ioband.
> I tested dm-ioband( the latest release, ver 1.7.0 ) IO controller, but
> I had a strange result from it.
> I have something wrong in test process?
> The test process and results are in attached file.
> Can you check my testing result and give me a helpful advices and comments?
There are some suggestions for you.
1. you have to specify a dm-ioband device at the command line to
control bandwidth.
# tiotest -R -d /dev/mapper/ioband1 -f 300
2. tiotest is not an appropriate tool to see how bandwith is shared
among devices, becasue those three tiotests don't finish at the
same time, a process which issues I/Os to a device with the highest
weight finishes first, so you can't see how bandwidth is shared
from the results of each tiotest.
I use iostat to see the time variation of bandiwdth. The followings
are the outputs of iostat just after starting three tiotests on the
same setting as yours.
# iostat -p dm-0 -p dm-1 -p dm-2 1
Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
dm-0 5430.00 0.00 10860.00 0 10860
dm-1 16516.00 0.00 16516.00 0 16516
dm-2 32246.00 0.00 32246.00 0 32246
avg-cpu: %user %nice %system %iowait %steal %idle
0.51 0.00 21.83 76.14 0.00 1.52
Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
dm-0 5720.00 0.00 11440.00 0 11440
dm-1 16138.00 0.00 16138.00 0 16138
dm-2 32734.00 0.00 32734.00 0 32734
...
> You can refer the testing tool, tiobench, in
> http://sourceforge.net/projects/tiobench/
> Originally, tiobench don't support the direct IO mode testing, so I
> added the O_DIRECT option to tiobench source code and recompile it to
> test the Direct IO cases
Could you give me the O_DIRECT patch?
Thanks,
Ryo Tsuruta
next prev parent reply other threads:[~2008-10-08 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 5:37 Ryo Tsuruta
2008-10-03 5:38 ` [PATCH 1/2] dm-ioband: I/O bandwidth controller v1.7.0: Source code and patch Ryo Tsuruta
2008-10-03 5:39 ` [PATCH 2/2] dm-ioband: I/O bandwidth controller v1.7.0: Document Ryo Tsuruta
2008-10-08 8:29 ` [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.7.0: Introduction Dong-Jae Kang
2008-10-08 10:40 ` Ryo Tsuruta [this message]
2008-10-09 6:15 ` Dong-Jae Kang
2008-10-09 12:14 ` Ryo Tsuruta
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=20081008.194022.226783199.ryov@valinux.co.jp \
--to=ryov@valinux.co.jp \
--cc=agk@sourceware.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=baramsori72@gmail.com \
--cc=containers@lists.linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=fernando@oss.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xemul@openvz.org \
--cc=xen-devel@lists.xensource.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
all inboxes | Powered by JetHome®