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: Thu, 30 Apr 2009 16:53:10 +0900 (JST) [thread overview]
Message-ID: <20090430.165310.226796026.ryov@valinux.co.jp> (raw)
In-Reply-To: <2891419e0904292215x240dfeeg71f3eed0066bc112@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: Thu, 30 Apr 2009 14:15:24 +0900
> Hi Ryo
>
> I am sorry for delayed reply.
> I tested range-bw policy as you send me your configuration
> and I found some logical bugs in range-bw including big scheduling overhead.
>
> > 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
> >
> > Please feel free to ask me if you need more information.
> >
> >
> > I'm look forward to seeing the results.
> >
> Thanks for your comments.
> And I will fix the bugs and re-release it after several days
> at that time, I inform you about that.
>
> Ryo,
> now, I am using bio-cgroup.....
> but, Is there additional things I have to consider to support AIO or
> dealyed I/O?
bio-cgroup is renamed to bklio-cgroup. :)
I don't clearly understand about range-bw but I think that you don't
need to consider to support them and it should be taken care of by
blkio-cgroup and the common part of dm-ioband, not the policy
implementation. Do you have any problems with AIO or delayed write?
>
> --
> Best Regards,
> Dong-Jae Kang
next prev parent reply other threads:[~2009-04-30 7:53 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 [this message]
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
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=20090430.165310.226796026.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®