LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ryo Tsuruta <ryov@valinux.co.jp>
To: andi@firstfloor.org
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: [PATCH 2/2] dm-band: The I/O bandwidth controller: Document
Date: Thu, 24 Jan 2008 19:32:02 +0900 (JST)	[thread overview]
Message-ID: <20080124.193202.193689962.ryov@valinux.co.jp> (raw)
In-Reply-To: <p73lk6g9uwq.fsf@bingen.suse.de>

Hi,

> > Here is the document of dm-band.
> 
> Could you please address in the document how the intended use
> cases/feature set etc. differs from CFQ2 io priorities?

Thank you for your suggestion, I'll do that step by step.

Thanks,
Ryo Tsuruta

  reply	other threads:[~2008-01-24 10:32 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 [this message]
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 ` [dm-devel] " Alasdair G Kergon
2008-01-23 16:21   ` 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=20080124.193202.193689962.ryov@valinux.co.jp \
    --to=ryov@valinux.co.jp \
    --cc=andi@firstfloor.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.com \
    --subject='Re: [PATCH 2/2] dm-band: The I/O bandwidth controller: Document' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).