public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: nauman@google.com, fernando@oss.ntt.co.jp,
	linux-kernel@vger.kernel.org, jmoyer@redhat.com,
	vgoyal@redhat.com, jens.axboe@oracle.com, agk@redhat.com,
	balbir@linux.vnet.ibm.com
Subject: Re: dm-ioband: Test results.
Date: Tue, 21 Apr 2009 09:57:23 -0400	[thread overview]
Message-ID: <20090421135723.GA13953@redhat.com> (raw)
In-Reply-To: <20090421.211051.183023683.ryov@valinux.co.jp>

On Tue, Apr 21 2009 at  8:10am -0400,
Ryo Tsuruta <ryov@valinux.co.jp> wrote:

> Hi Nauman,
> 
> > > The real question is, once you create a version of dm-ioband that
> > > co-operates with CFQ scheduler, how that solution would compare with
> > > the patch set Vivek has posted? In my opinion, we need to converge to
> > > one solution as soon as possible, so that we can work on it together
> > > to refine and test it.
> > 
> > I think I can do some help for your work. but I want to continue the
> > development of dm-ioband, because dm-ioband actually works well and
> > I think it has some advantages against other IO controllers.
> >   - It can use without cgroup.
> >   - It can control bandwidth on a per partition basis.
> >   - The driver module can be replaced without stopping the system.
> 
> In addition, dm-ioband can run on the RHEL5.

RHEL5 compatibility does not matter relative to merging an I/O bandwidth
controller upstream.  So both the "can [be] use without cgroup" and "can
run on RHEL5" features do not help your cause of getting dm-ioband
merged upstream.  In fact these features serve as distractions.

Mike

  reply	other threads:[~2009-04-21 13:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13  4:05 dm-ioband: Test results Ryo Tsuruta
2009-04-13 14:46 ` Vivek Goyal
2009-04-14  2:49   ` Vivek Goyal
2009-04-14  5:27     ` Ryo Tsuruta
2009-04-14  9:30   ` [dm-devel] " Ryo Tsuruta
2009-04-15 17:04     ` Vivek Goyal
2009-04-16 12:56       ` Ryo Tsuruta
2009-04-16 13:32         ` Vivek Goyal
2009-04-15  4:37 ` Vivek Goyal
2009-04-15 13:38   ` Ryo Tsuruta
2009-04-15 14:10     ` Vivek Goyal
2009-04-15 16:17     ` Vivek Goyal
2009-04-16  2:47     ` [dm-devel] " Ryo Tsuruta
2009-04-16 14:11       ` Vivek Goyal
2009-04-16 20:24         ` Nauman Rafique
2009-04-20  8:29           ` Ryo Tsuruta
2009-04-20  9:07             ` Nauman Rafique
2009-04-21 12:06               ` Ryo Tsuruta
2009-04-21 12:10                 ` Ryo Tsuruta
2009-04-21 13:57                   ` Mike Snitzer [this message]
2009-04-21 14:16                     ` Vivek Goyal
2009-04-22  0:50                       ` Li Zefan
2009-04-22  3:14                       ` [dm-devel] " Ryo Tsuruta
2009-04-22 15:18                         ` Mike Snitzer
2009-04-27 10:30                           ` Ryo Tsuruta
2009-04-27 12:44                             ` Ryo Tsuruta
2009-04-27 13:03                             ` Mike Snitzer
2009-04-20 21:37             ` [dm-devel] " Vivek Goyal
2009-04-21 12:18               ` Ryo Tsuruta
2009-04-16 20:57 ` Vivek Goyal
2009-04-17  2:11   ` Vivek Goyal
2009-04-17  2:28     ` Vivek Goyal

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=20090421135723.GA13953@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=dm-devel@redhat.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=jens.axboe@oracle.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nauman@google.com \
    --cc=vgoyal@redhat.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