Linux Container Development
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org>
To: Ryo Tsuruta <ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview
Date: Wed, 23 Jan 2008 15:32:35 +0100	[thread overview]
Message-ID: <1201098755.6341.54.camel@lappy> (raw)
In-Reply-To: <20080123.215350.193721890.ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>


On Wed, 2008-01-23 at 21:53 +0900, Ryo Tsuruta wrote:
> Hi everyone,
> 
> I'm happy to announce that I've implemented a Block I/O bandwidth controller.
> The controller is designed to be of use in a cgroup or virtual machine
> environment. The current approach is that the controller is implemented as
> a device-mapper driver.

What definition of bandwidth does it use? Does it for example account
for seek latency?

  parent reply	other threads:[~2008-01-23 14:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080123.215350.193721890.ryov@valinux.co.jp>
     [not found] ` <20080123.215632.226773739.ryov@valinux.co.jp>
     [not found]   ` <20080123.215632.226773739.ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
2008-01-23 13:33     ` [PATCH 1/2] dm-band: The I/O bandwidth controller: Source code patch Frans Pop
     [not found]   ` <E1JHfjM-0003NV-BR@faramir.fjphome.nl>
     [not found]     ` <E1JHfjM-0003NV-BR-QuJFzwv6nO7YRozH8XE8NfP6llvjuJOh@public.gmane.org>
2008-01-23 15:48       ` Ryo Tsuruta
2008-01-27 15:44       ` Frans Pop
     [not found] ` <20080123.215350.193721890.ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
2008-01-23 12:56   ` Ryo Tsuruta
2008-01-23 12:58   ` [PATCH 2/2] dm-band: The I/O bandwidth controller: Document Ryo Tsuruta
2008-01-23 14:32   ` Peter Zijlstra [this message]
2008-01-23 17:25     ` [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview Ryo Tsuruta
2008-01-23 14:47   ` [dm-devel] " Alasdair G Kergon
2008-01-25  7:07   ` dm-band: The I/O bandwidth controller: Performance Report Ryo Tsuruta
     [not found] ` <20080123144717.GS8075@agk.fab.redhat.com>
     [not found]   ` <20080123144717.GS8075-swAlYijrCMMf7BdofF/totBPR1lH4CV8@public.gmane.org>
2008-01-23 16:21     ` [dm-devel] [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview Hirokazu Takahashi
     [not found] ` <20080123.215844.71118155.ryov@valinux.co.jp>
     [not found]   ` <20080123.215844.71118155.ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
2008-01-23 19:57     ` [PATCH 2/2] dm-band: The I/O bandwidth controller: Document Andi Kleen
     [not found]   ` <p73lk6g9uwq.fsf@bingen.suse.de>
     [not found]     ` <p73lk6g9uwq.fsf-KvMlXPVkKihbpigZmTR7Iw@public.gmane.org>
2008-01-24 10:32       ` Ryo Tsuruta
     [not found] ` <20080125.160720.183032233.ryov@valinux.co.jp>
     [not found]   ` <20080125.160720.183032233.ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
2008-01-29  6:42     ` [Xen-devel] dm-band: The I/O bandwidth controller: Performance Report INAKOSHI Hiroya
     [not found]   ` <479ECAC9.5070709@jp.fujitsu.com>
     [not found]     ` <479ECAC9.5070709-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2008-01-30  3:32       ` Ryo Tsuruta
     [not found] <20080123.215350.193721890.ryov__34610.100350301$1201092994$gmane$org@valinux.co.jp>
     [not found] ` <20080123.215350.193721890.ryov__34610.100350301$1201092994$gmane$org-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
2008-01-23 19:22   ` [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview Anthony Liguori
     [not found] ` <479793FC.70701@codemonkey.ws>
     [not found]   ` <479793FC.70701-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2008-01-24  8:11     ` Hirokazu Takahashi
2008-01-23 12:53 Ryo Tsuruta

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=1201098755.6341.54.camel@lappy \
    --to=a.p.zijlstra-/nlkjasks4vmr6xm/wnwpw@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org \
    --cc=virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
    /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