LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ryo Tsuruta <ryov@valinux.co.jp>
To: zumeng.chen@windriver.com
Cc: agk@redhat.com, linux-kernel@vger.kernel.org,
	dm-devel@redhat.com, containers@lists.linux-foundation.org,
	virtualization@lists.linux-foundation.org,
	xen-devel@lists.xensource.com, fernando@oss.ntt.co.jp
Subject: Re: [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.8.0: Introduction
Date: Wed, 22 Oct 2008 19:38:31 +0900 (JST)	[thread overview]
Message-ID: <20081022.193831.193716981.ryov@valinux.co.jp> (raw)
In-Reply-To: <48FDB8AC.9020707@windriver.com>

Hi Chen,

> I applied your patches(both) into the latest kernel(27), and dm-ioband
> looks work well(other than schedule_timeout in alloc_ioband_device);
> But I think you are the author of bio_tracking, so it is high
> appreciated if you can give your comments and advices for potential
> difference between 27-rc5-mm1 and 2.6.27 to me.

There is no major difference between both version, but I have no time
to port and test bio-cgroup to/on 2.6.27.

Kamezawa-san said
> the newest mmotm has the newest *big* change. enjoy it ;)

The next bio-cgroup patch will be based on this newest change.

Thanks,
Ryo Tsuruta

      parent reply	other threads:[~2008-10-22 10:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  7:09 Ryo Tsuruta
2008-10-17  7:10 ` [PATCH 1/2] dm-ioband: I/O bandwidth controller v1.8.0: Source code and patch Ryo Tsuruta
2008-10-17  7:11   ` [PATCH 2/2] dm-ioband: I/O bandwidth controller v1.8.0: Document Ryo Tsuruta
2008-10-20  8:40 ` [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.8.0: Introduction Dong-Jae Kang
2008-10-20  9:01   ` Ryo Tsuruta
2008-10-20 10:13     ` Dong-Jae Kang
2008-10-20 12:48       ` Ryo Tsuruta
2008-10-21  2:00         ` KAMEZAWA Hiroyuki
2008-10-21 11:10 ` Chen Zumeng
2008-10-22  7:55   ` Chen Zumeng
2008-10-22  8:05     ` Ryo Tsuruta
2008-10-22  8:12       ` Chen Zumeng
2008-10-23 10:02       ` haotian
2008-10-23 11:28         ` Ryo Tsuruta
2008-10-22 10:38   ` Ryo Tsuruta [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=20081022.193831.193716981.ryov@valinux.co.jp \
    --to=ryov@valinux.co.jp \
    --cc=agk@redhat.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=zumeng.chen@windriver.com \
    --subject='Re: [PATCH 0/2] dm-ioband: I/O bandwidth controller v1.8.0: Introduction' \
    /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).