From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754240AbZEFAf0 (ORCPT ); Tue, 5 May 2009 20:35:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753135AbZEFAfK (ORCPT ); Tue, 5 May 2009 20:35:10 -0400 Received: from rv-out-0506.google.com ([209.85.198.230]:30028 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753038AbZEFAfG convert rfc822-to-8bit (ORCPT ); Tue, 5 May 2009 20:35:06 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=r17ndfTSdQ/MseJqr4aQ3zVp9zISsupiMJ1+RqUowmP7Yf3bEp8YLFeKQrRacyWtvU HKXuRHDDyAwUr/vsA2T3C16eWPExS8bK9jnINSYk9+kbkQgv6pwgiHFPIubSxU+kKPjS EvbM0z4eAGgPeiACHHyDXdDuA1sVKOAaFwZBc= MIME-Version: 1.0 In-Reply-To: <20090505.073655.193711315.ryov@valinux.co.jp> References: <2891419e0904292215x240dfeeg71f3eed0066bc112@mail.gmail.com> <20090430.165310.226796026.ryov@valinux.co.jp> <2891419e0905040423y27f25ce7y61e5211aded85f99@mail.gmail.com> <20090505.073655.193711315.ryov@valinux.co.jp> Date: Wed, 6 May 2009 09:35:03 +0900 Message-ID: <2891419e0905051735s7371e590gc942e4c6c475aa67@mail.gmail.com> Subject: Re: [PATCH] range-bw: Another I/O scheduling policy of dm-ioband supporting the predicable I/O bandwidth (range bandwidth) From: Dong-Jae Kang To: Ryo Tsuruta 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 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2009/5/5 Ryo Tsuruta : > Hi Dong-Jae > > From: Dong-Jae Kang > 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 ? > > O.K. I'll check it and report back to you. > Hi Ryo, Thank you for your kindness I am looking forward to your report. >> >> > 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? >> >> if you are interested in range-bw, more information is available to you >> and any questions and comments about range-bw is always welcom.  :) >> >> Ryo, >> blkio-cgroup can be applied to dm-ioband ver1.10.3 without modification? >> I didn't check blkio-cgroup yet. > > Yes, it can. Please try it. > Okay, I will try to apply and test it. and then, If I have any questions and problems about that, I will contact you again. Thank you. -- Best Regards, Dong-Jae Kang