From: Alasdair G Kergon <agk@redhat.com>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
containers@lists.linux-foundation.org,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xensource.com
Subject: Re: [dm-devel] [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview
Date: Wed, 23 Jan 2008 14:47:17 +0000 [thread overview]
Message-ID: <20080123144717.GS8075@agk.fab.redhat.com> (raw)
In-Reply-To: <20080123.215350.193721890.ryov@valinux.co.jp>
On Wed, Jan 23, 2008 at 09:53:50PM +0900, Ryo Tsuruta wrote:
> Dm-band gives bandwidth to each job according to its weight,
> which each job can set its own value to.
> At this time, a job is a group of processes with the same pid or pgrp or uid.
It seems to rely on 'current' to classify bios and doesn't do it until the map
function is called, possibly in a different process context, so it won't
always identify the original source of the I/O correctly: people need to take
this into account when designing their group configuration and so this should
be mentioned in the documentation.
I've uploaded it here while we consider ways we might refine the architecture and
interfaces etc.:
http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/dm-add-band-target.patch
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2008-01-23 14:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 12:53 [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview Ryo Tsuruta
2008-01-23 12:56 ` [PATCH 1/2] dm-band: The I/O bandwidth controller: Source code patch Ryo Tsuruta
2008-01-23 13:33 ` Frans Pop
2008-01-23 15:48 ` Ryo Tsuruta
2008-01-27 15:44 ` Frans Pop
2008-01-23 12:58 ` [PATCH 2/2] dm-band: The I/O bandwidth controller: Document Ryo Tsuruta
2008-01-23 19:57 ` Andi Kleen
2008-01-24 10:32 ` Ryo Tsuruta
2008-01-23 14:32 ` [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview Peter Zijlstra
2008-01-23 17:25 ` Ryo Tsuruta
2008-01-23 14:47 ` Alasdair G Kergon [this message]
2008-01-23 16:21 ` [dm-devel] " Hirokazu Takahashi
2008-01-24 3:38 ` YAMAMOTO Takashi
2008-01-24 10:14 ` Hirokazu Takahashi
2008-01-25 6:26 ` YAMAMOTO Takashi
2008-01-25 7:07 ` dm-band: The I/O bandwidth controller: Performance Report Ryo Tsuruta
2008-01-29 6:42 ` [Xen-devel] " INAKOSHI Hiroya
2008-01-30 3:32 ` 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=20080123144717.GS8075@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=containers@lists.linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryov@valinux.co.jp \
--cc=virtualization@lists.linux-foundation.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