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: Fri, 24 Apr 2009 18:58:23 +0900 (JST) [thread overview]
Message-ID: <20090424.185823.104059944.ryov@valinux.co.jp> (raw)
In-Reply-To: <2891419e0904230210w40482535ma3fc25c1e429969d@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: Text/Plain; charset=utf-8, Size: 1756 bytes --]
Hi Dong-Jae,
> range-bw is based on newest version of dm-ioband, bio-cgroup V7(4
> patch files), dm-ioband-V1.10.3(1 patch file) and these can be
> referred in
> http://people.valinux.co.jp/~ryov/dm-ioband/
> http://people.valinux.co.jp/~ryov/bio-cgroup/
> and the below range-bw patch file(dm-ioband-rangebw-1.10.3.patch)
> including Ryoâs patch set is also referred in:
> http://www.corsetproject.net/browser/corset_source_code/resource_controllers/disk_controller/Range-BW-for-dmioband-V1.10.3
> You have to apply this(dm-ioband-rangebw-1.10.3.patch) patch file
> after applying dm-ioband and bio-cgroup patches.
>
> The released range-bw may have some problems and improper code
> although I try to test heavily. It is first release ^^
> And it is required to reduce the overhead of I/O scheduling and to
> optimize the source code.
> Any comments or advices is welcome
>
> Ryo Tsuruta, Can you check this patch file ?
> for convenience, patch file is attached in this mail.
I took a quick look at your patch. It seems to be no problem for
existing dm-ioband code, but I would suggest you that you had better
use checkpatch.pl to check for your coding style.
The patch could be applied and compiled successfully. I did a simple
test, running fio on each cgroup in 30 seconds simultaneously, and got
the following results.
w/o range-bw w/ range-bw (min&max-bw settings)
cgroup1 331KB/s 102KB/s (100KB)
cgroup2 331KB/s 196KB/s (200KB)
Do you have any benchmark resutls? I'd be very interested to see it.
Thanks,
Ryo Tsuruta
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2009-04-24 9:58 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 [this message]
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
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=20090424.185823.104059944.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®