[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081114.103828.737004071327928691.ryov@valinux.co.jp>
Date: Fri, 14 Nov 2008 10:38:28 +0900 (JST)
From: Ryo Tsuruta <ryov@...inux.co.jp>
To: dm-devel@...hat.com, taka@...inux.co.jp
Cc: psusi@....rr.com, xen-devel@...ts.xensource.com,
containers@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, agk@...rceware.org,
xemul@...nvz.org, fernando@....ntt.co.jp,
kamezawa.hiroyu@...fujitsu.com, balbir@...ux.vnet.ibm.com
Subject: Re: [dm-devel] [PATCH 1/8] dm-ioband: Introduction
Hi Phillip,
> > Ryo Tsuruta wrote:
> > > Create two ioband devices "ioband1" and "ioband2". "ioband1" is mapped
> > > to "/dev/sda1" and has a weight of 40. "ioband2" is mapped to "/dev/sda2"
> > > and has a weight of 10. "ioband1" can use 80% --- 40/(40+10)*100 ---
> > > of the bandwidth of the physical disk "/dev/sda" while "ioband2" can use 20%.
> >
> > Just to clarify, when you say ioband1 can use 80% of the bandwidh, you
> > mean that is how much it will get if both io bands are loaded right? If
> > there is no activity on ioband2, then ioband1 will get the full disk
> > bandwidth right?
>
> Absolutely, you are right!
Here is a benchmark result of sharing bandwidth between three ioband
devices. When there is no activity on ioband2, the total bandwidth of
the disk is shared only between ioband1 and ioband3 according to their
weights.
http://people.valinux.co.jp/~ryov/dm-ioband/benchmark/partition1.html
--
Ryo Tsuruta <ryov@...inux.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists