From: Phillip Susi <psusi@cfl.rr.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xensource.com, fernando@oss.ntt.co.jp,
balbir@linux.vnet.ibm.com, xemul@openvz.org,
kamezawa.hiroyu@jp.fujitsu.com, agk@sourceware.org
Subject: Re: [dm-devel] [PATCH 1/8] dm-ioband: Introduction
Date: Thu, 13 Nov 2008 14:36:43 -0500 [thread overview]
Message-ID: <491C81CB.7010705@cfl.rr.com> (raw)
In-Reply-To: <20081113.121146.623571555980959797.ryov@valinux.co.jp>
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?
next prev parent reply other threads:[~2008-11-13 19:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 3:10 [PATCH 0/8] I/O bandwidth controller and BIO tracking Ryo Tsuruta
2008-11-13 3:11 ` [PATCH 1/8] dm-ioband: Introduction Ryo Tsuruta
2008-11-13 3:12 ` [PATCH 2/8] dm-ioband: Source code and patch Ryo Tsuruta
2008-11-13 3:12 ` [PATCH 3/8] dm-ioband: Document Ryo Tsuruta
2008-11-13 3:13 ` [PATCH 4/8] bio-cgroup: Introduction Ryo Tsuruta
2008-11-13 3:13 ` [PATCH 5/8] bio-cgroup: The new page_cgroup framework Ryo Tsuruta
2008-11-13 3:14 ` [PATCH 6/8] bio-cgroup: The body of bio-cgroup Ryo Tsuruta
2008-11-13 3:15 ` [PATCH 7/8] bio-cgroup: Page tracking hooks Ryo Tsuruta
2008-11-13 3:15 ` [PATCH 8/8] bio-cgroup: Add a cgroup support to dm-ioband Ryo Tsuruta
2008-11-14 7:01 ` [PATCH 6/8] bio-cgroup: The body of bio-cgroup Takuya Yoshikawa
2008-11-16 11:46 ` Hirokazu Takahashi
2008-11-17 7:50 ` [PATCH 6/8]Re: " Takuya Yoshikawa
2008-11-13 19:36 ` Phillip Susi [this message]
2008-11-13 23:18 ` [dm-devel] [PATCH 1/8] dm-ioband: Introduction Hirokazu Takahashi
2008-11-14 1:38 ` Ryo Tsuruta
2008-11-13 6:30 ` [PATCH 0/8] I/O bandwidth controller and BIO tracking KAMEZAWA Hiroyuki
2008-11-13 7:26 ` [dm-devel] " Hirokazu Takahashi
2008-11-13 16:20 ` Balbir Singh
2008-11-13 23:15 ` Hirokazu Takahashi
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=491C81CB.7010705@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=agk@sourceware.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=fernando@oss.ntt.co.jp \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xemul@openvz.org \
--cc=xen-devel@lists.xensource.com \
/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