From: Alasdair G Kergon <agk@redhat.com>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.10.0: Introduction
Date: Tue, 20 Jan 2009 15:04:31 +0000 [thread overview]
Message-ID: <20090120150431.GF9859@agk.fab.redhat.com> (raw)
In-Reply-To: <20090120.141022.193708059.ryov@valinux.co.jp>
By the way, you'll notice I've combined the three messages into a single
patch: there seems little point applying the documentation as a separate
patch.
http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/dm-add-ioband.patch
When sending revisions, either send a fresh patch that is a drop-in
replacement for what I have included, or alternatively send a patch to
be applied after what I have got. (The second way helps people on the
list see what you are changing without needing to perform their own
diffs, and I'll simply fold it into the patch I have.)
Alasdair
--
agk@redhat.com
prev parent reply other threads:[~2009-01-20 15:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 5:10 [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.10.0: Introduction Ryo Tsuruta
2009-01-20 5:11 ` [PATCH 1/2] dm-ioband: I/O bandwidth controller v1.10.0: Source code and patch Ryo Tsuruta
2009-01-20 5:12 ` [PATCH 2/2] dm-ioband: I/O bandwidth controller v1.10.0: Document Ryo Tsuruta
2009-01-20 14:52 ` [PATCH 1/2] dm-ioband: I/O bandwidth controller v1.10.0: Source code and patch Alasdair G Kergon
2009-01-21 13:03 ` Ryo Tsuruta
2009-01-21 17:18 ` Alasdair G Kergon
2009-01-22 12:05 ` Ryo Tsuruta
2009-02-04 5:07 ` Ryo Tsuruta
2009-01-20 15:19 ` Alasdair G Kergon
2009-01-20 15:53 ` Alasdair G Kergon
[not found] ` <20090120155334.GH9859-swAlYijrCMMf7BdofF/totBPR1lH4CV8@public.gmane.org>
2009-01-22 16:12 ` [dm-devel] " Vivek Goyal
2009-01-22 16:12 ` Vivek Goyal
2009-01-23 10:14 ` Ryo Tsuruta
2009-01-26 16:29 ` Vivek Goyal
2009-01-29 3:36 ` 2-Level IO scheduling (Re: [dm-devel] [PATCH 1/2] dm-ioband: I/O bandwidth controller v1.10.0: Source code and patch) Ryo Tsuruta
2009-01-29 3:39 ` Hierarchical grouping facility for IO controller " Ryo Tsuruta
2009-01-29 3:41 ` Implementation of dm-ioband as a dm-driver " Ryo Tsuruta
[not found] ` <20090126162951.GI31802-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-01-29 3:36 ` 2-Level IO scheduling " Ryo Tsuruta
2009-01-29 3:39 ` Hierarchical grouping facility for IO controller " Ryo Tsuruta
2009-01-29 3:41 ` Implementation of dm-ioband as a dm-driver " Ryo Tsuruta
[not found] ` <20090123.191404.39168431.ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
2009-01-26 16:29 ` [dm-devel] [PATCH 1/2] dm-ioband: I/O bandwidth controller v1.10.0: Source code and patch Vivek Goyal
[not found] ` <20090122161218.GA28795-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-01-23 10:14 ` Ryo Tsuruta
2009-01-20 15:04 ` Alasdair G Kergon [this message]
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=20090120150431.GF9859@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ryov@valinux.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.