From: Andrew Morton <akpm@linux-foundation.org>
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, agk@sourceware.org,
Sergey Kononenko <sergk@sergk.org.ua>
Subject: Re: [PATCH 2/2] dm-ioband: I/O bandwidth controller v0.0.4: Document
Date: Sat, 26 Apr 2008 11:45:35 -0700 [thread overview]
Message-ID: <20080426114535.e19283be.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080424.202219.59667073.ryov@valinux.co.jp>
On Thu, 24 Apr 2008 20:22:19 +0900 (JST) Ryo Tsuruta <ryov@valinux.co.jp> wrote:
> +What's dm-ioband all about?
> +
> + dm-ioband is an I/O bandwidth controller implemented as a device-mapper
> + driver. Several jobs using the same physical device have to share the
> + bandwidth of the device. dm-ioband 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. There is also a plan to make it support cgroup. A job can also be a
> + virtual machine such as KVM or Xen.
Most writes are performed by pdflush, kswapd, etc. This will lead to large
inaccuracy.
It isn't trivial to fix. We'd need deep, long tracking of ownership
probably all the way up to the pagecache page. The same infrastructure
would be needed to make Sergey's "BSD acct: disk I/O accounting" vaguely
accurate. Other proposals need it, but I forget what they are.
Much more minor points: when merge-time comes, the patches should have the
LINUX_VERSION_CODE stuff removed. And probably all of the many `inline's
should be removed.
next prev parent reply other threads:[~2008-04-26 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 11:18 [PATCH 0/2] dm-ioband: I/O bandwidth controller v0.0.4: Introduction Ryo Tsuruta
2008-04-24 11:21 ` [PATCH 1/2] dm-ioband: I/O bandwidth controller v0.0.4: Source code and patch Ryo Tsuruta
2008-04-24 11:22 ` [PATCH 2/2] dm-ioband: I/O bandwidth controller v0.0.4: Document Ryo Tsuruta
2008-04-26 18:45 ` Andrew Morton [this message]
2008-04-28 6:49 ` Hirokazu Takahashi
2008-04-28 8:06 ` 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=20080426114535.e19283be.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agk@sourceware.org \
--cc=containers@lists.linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryov@valinux.co.jp \
--cc=sergk@sergk.org.ua \
--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