From: Ryo Tsuruta <ryov@valinux.co.jp>
To: baramsori72@gmail.com
Cc: righi.andrea@gmail.com, menage@google.com,
balbir@linux.vnet.ibm.com, guijianfeng@cn.fujitsu.com,
kamezawa.hiroyu@jp.fujitsu.com, agk@sourceware.org,
akpm@linux-foundation.org, axboe@kernel.dk, chlunde@ping.uio.no,
dave@linux.vnet.ibm.com, dpshah@google.com,
eric.rannaud@gmail.com, fernando@oss.ntt.co.jp,
taka@valinux.co.jp, lizf@cn.fujitsu.com, matt@bluehost.com,
dradford@bluehost.com, ngupta@google.com,
randy.dunlap@oracle.com, roberto@unbit.it,
s-uchida@ap.jp.nec.com, subrata@linux.vnet.ibm.com,
yoshikawa.takuya@oss.ntt.co.jp, nauman@google.com,
fchecconi@gmail.com, paolo.valente@unimore.it,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, corsetproject@googlegroups.com
Subject: Re: [PATCH] range-bw: Another I/O scheduling policy of dm-ioband supporting the predicable I/O bandwidth (range bandwidth)
Date: Tue, 12 May 2009 20:30:14 +0900 (JST) [thread overview]
Message-ID: <20090512.203014.71110404.ryov@valinux.co.jp> (raw)
In-Reply-To: <2891419e0905051735s7371e590gc942e4c6c475aa67@mail.gmail.com>
Hi Dong-Jae,
From: Dong-Jae Kang <baramsori72@gmail.com>
Subject: Re: [PATCH] range-bw: Another I/O scheduling policy of dm-ioband supporting the predicable I/O bandwidth (range bandwidth)
Date: Wed, 6 May 2009 09:35:03 +0900
> 2009/5/5 Ryo Tsuruta <ryov@valinux.co.jp>:
> > Hi Dong-Jae
> >
> > From: Dong-Jae Kang <baramsori72@gmail.com>
> > Subject: Re: [PATCH] range-bw: Another I/O scheduling policy of dm-ioband supporting the predicable I/O bandwidth (range bandwidth)
> > Date: Mon, 4 May 2009 20:23:04 +0900
> >
> >> Hi, Ryo
> >>
> >> I released bug-fixed range-bw(V1) controller several minutes ago
> >>
> >> Although several WARNINGs of checkpatch are remained,
> >> but patch file was strictly checked by checkpatch.pl
> >> It was very time-consuming job :)
> >> Thank you for your advice
> >>
> >> >>
> >> >> > I used fio 1.22. The below is a script which I actually ran.
> >> >> >
> >> >> > #!/bin/sh
> >> >> > dev1=/dev/sdb4 # SATA disk
> >> >> > echo "0 $(sudo blockdev --getsize $dev1) ioband $dev1 share2 0 0
> >> >> > cgroup range-bw 0" | sudo dmsetup create ioband1
> >> >> >
> >> >> > arg="--time_based --runtime=10 --ioengine=libaio --iodepth=50 \
> >> >> > --direct=1 --norandommap"
> >> >> >
> >> >> > dmsetup message ioband1 0 attach 2
> >> >> > dmsetup message ioband1 0 attach 3
> >> >> > dmsetup message ioband1 0 min-bw 2:100
> >> >> > dmsetup message ioband1 0 max-bw 2:100
> >> >> > dmsetup message ioband1 0 min-bw 3:200
> >> >> > dmsetup message ioband1 0 max-bw 3:200
> >> >>
> >> >> I recommend it is better to use different value in min-bw and max-bw
> >> >> because its concept is to support range-bw with the minimum
> >> >> guaranteeing and maximum limitation.
> >> >> exampe - min-bw : 1024 / max-bw : 3072
> >> >>
> >> >> > echo $$ > /cgroup/grp1/tasks
> >> >> > fio $arg --rw=randread --name=grp1 --filename=/dev/mapper/ioband1 \
> >> >> > --output=r2-1.log &
> >> >> > echo $$ > /cgroup/grp2/tasks
> >> >> > fio $arg --rw=randread --name=grp2 --filename=/dev/mapper/ioband1 \
> >> >> > --output=r2-2.log &
> >> >> > wait
> >>
> >> after bug-fix,I evaluated range-bw according to your configuration and
> >> test environment
> >> the result is in new relesed range-bw mail, [PATCH 0/2]
> >> and more detailed documentation is also available and it can be
> >> referred in [PATCH 1/2]
> >>
> >> Ryo,
> >> can you check the result ?
I did the same test as before and got the results as expected.
cgroup1 cgroup2
min:max-bw 0:100 0:200
-------------------------------------
read 100 197
write 103 198 [KB/s]
I got errors while applying your patch, some lines are wrapped with
carriage returns.
+extern int policy_range_bw_init(struct ioband_device *dp, int argc,
>> char **argv);
Thanks,
Ryo Tsuruta
next prev parent reply other threads:[~2009-05-12 11:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 9:10 Dong-Jae Kang
2009-04-24 9:58 ` Ryo Tsuruta
2009-04-27 8:58 ` Dong-Jae Kang
2009-04-27 11:12 ` Ryo Tsuruta
2009-04-30 5:15 ` Dong-Jae Kang
2009-04-30 7:53 ` Ryo Tsuruta
2009-05-04 11:23 ` Dong-Jae Kang
2009-05-04 22:36 ` Ryo Tsuruta
2009-05-06 0:35 ` Dong-Jae Kang
2009-05-12 11:30 ` Ryo Tsuruta [this message]
2009-05-15 7:00 ` Dong-Jae Kang
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=20090512.203014.71110404.ryov@valinux.co.jp \
--to=ryov@valinux.co.jp \
--cc=agk@sourceware.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=balbir@linux.vnet.ibm.com \
--cc=baramsori72@gmail.com \
--cc=chlunde@ping.uio.no \
--cc=containers@lists.linux-foundation.org \
--cc=corsetproject@googlegroups.com \
--cc=dave@linux.vnet.ibm.com \
--cc=dpshah@google.com \
--cc=dradford@bluehost.com \
--cc=eric.rannaud@gmail.com \
--cc=fchecconi@gmail.com \
--cc=fernando@oss.ntt.co.jp \
--cc=guijianfeng@cn.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=matt@bluehost.com \
--cc=menage@google.com \
--cc=nauman@google.com \
--cc=ngupta@google.com \
--cc=paolo.valente@unimore.it \
--cc=randy.dunlap@oracle.com \
--cc=righi.andrea@gmail.com \
--cc=roberto@unbit.it \
--cc=s-uchida@ap.jp.nec.com \
--cc=subrata@linux.vnet.ibm.com \
--cc=taka@valinux.co.jp \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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®