mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dong-Jae Kang <baramsori72@gmail.com>
To: Ryo Tsuruta <ryov@valinux.co.jp>
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: Mon, 27 Apr 2009 17:58:52 +0900	[thread overview]
Message-ID: <2891419e0904270158n71b25271p6094feba70d0555d@mail.gmail.com> (raw)
In-Reply-To: <20090424.185823.104059944.ryov@valinux.co.jp>

[-- Attachment #1: Type: text/plain, Size: 2611 bytes --]

Hi Ryo Tsuruta,

2009/4/24 Ryo Tsuruta <ryov@valinux.co.jp>:
> 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
>

Thank you for your comments about range-bw
and your recommendation of checkpatch.pl seems to be useful for me.

I wonder your test configuration and environment.
Your result  is some strange for me, because I didn't use the testing tool, fio.
I have used xdd, bonnie++ and tiobench during the test.

So, I will try to evaluate range-bw using fio, to do that, I need to
know your configuration and basic environment in briefly
if it don't bother you, can you give me the information?

and I attached the result of basic evaluation of range-bw using xdd
6.5.(Test Result for range-bw_english.pdf)
it was performed to evaluate the basic functionalities in one process per group.

actually, more evaluation is need in specfic envinronment like as
massive I/O by huge processes in each group.
and it is going on now
-- 
Best Regards,
Dong-Jae Kang

[-- Attachment #2: Test Result for range-bw_english.pdf --]
[-- Type: application/pdf, Size: 70132 bytes --]

  reply	other threads:[~2009-04-27  8:59 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 [this message]
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=2891419e0904270158n71b25271p6094feba70d0555d@mail.gmail.com \
    --to=baramsori72@gmail.com \
    --cc=agk@sourceware.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=balbir@linux.vnet.ibm.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=ryov@valinux.co.jp \
    --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®