From: Mike Snitzer <snitzer@redhat.com>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: fernando@oss.ntt.co.jp, dm-devel@redhat.com,
linux-kernel@vger.kernel.org, jmoyer@redhat.com, agk@redhat.com,
jens.axboe@oracle.com, nauman@google.com, vgoyal@redhat.com,
balbir@linux.vnet.ibm.com
Subject: Re: dm-ioband: Test results.
Date: Mon, 27 Apr 2009 09:03:32 -0400 [thread overview]
Message-ID: <20090427130331.GB3872@redhat.com> (raw)
In-Reply-To: <20090427.193006.112614137.ryov@valinux.co.jp>
On Mon, Apr 27 2009 at 6:30am -0400,
Ryo Tsuruta <ryov@valinux.co.jp> wrote:
> Hi Mike,
>
> > Why is it that you repeatedly ignore concern/discussion about your
> > determination to continue using a custom grouping mechanism? It is this
> > type of excess layering that serves no purpose other than to facilitate
> > out-of-tree use-cases. dm-ioband would take a big step closer to being
> > merged upstream if you took others' feedback and showed more willingness
> > to work through the outstanding issues.
>
> I think dm-ioband's approach is one simple way to handle cgroup
> because the current cgroup has no way to manage kernel module's
> resources. Please tell me if you have any good ideas to handle
> cgroup by dm-ioband.
If you'd like to keep dm-ioband modular then I'd say the appropriate
cgroup interfaces need to be exposed for module use (symbols exported,
etc). No other controller has had a need to be modular but if you think
it is requirement for dm-ioband (facilitate updates, etc) then I have to
believe it is doable.
Mike
WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@redhat.com>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: dm-devel@redhat.com, vgoyal@redhat.com, fernando@oss.ntt.co.jp,
linux-kernel@vger.kernel.org, jmoyer@redhat.com,
jens.axboe@oracle.com, nauman@google.com, agk@redhat.com,
balbir@linux.vnet.ibm.com
Subject: Re: dm-ioband: Test results.
Date: Mon, 27 Apr 2009 09:03:32 -0400 [thread overview]
Message-ID: <20090427130331.GB3872@redhat.com> (raw)
In-Reply-To: <20090427.193006.112614137.ryov@valinux.co.jp>
On Mon, Apr 27 2009 at 6:30am -0400,
Ryo Tsuruta <ryov@valinux.co.jp> wrote:
> Hi Mike,
>
> > Why is it that you repeatedly ignore concern/discussion about your
> > determination to continue using a custom grouping mechanism? It is this
> > type of excess layering that serves no purpose other than to facilitate
> > out-of-tree use-cases. dm-ioband would take a big step closer to being
> > merged upstream if you took others' feedback and showed more willingness
> > to work through the outstanding issues.
>
> I think dm-ioband's approach is one simple way to handle cgroup
> because the current cgroup has no way to manage kernel module's
> resources. Please tell me if you have any good ideas to handle
> cgroup by dm-ioband.
If you'd like to keep dm-ioband modular then I'd say the appropriate
cgroup interfaces need to be exposed for module use (symbols exported,
etc). No other controller has had a need to be modular but if you think
it is requirement for dm-ioband (facilitate updates, etc) then I have to
believe it is doable.
Mike
next prev parent reply other threads:[~2009-04-27 13:03 UTC|newest]
Thread overview: 55+ 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-13 14:46 ` Vivek Goyal
2009-04-14 2:49 ` Vivek Goyal
2009-04-14 2:49 ` Vivek Goyal
2009-04-14 5:27 ` Ryo Tsuruta
2009-04-14 9:30 ` Ryo Tsuruta
2009-04-14 9:30 ` [dm-devel] " Ryo Tsuruta
2009-04-15 17:04 ` Vivek Goyal
2009-04-15 17:04 ` [dm-devel] " Vivek Goyal
2009-04-16 12:56 ` Ryo Tsuruta
2009-04-16 12:56 ` Ryo Tsuruta
2009-04-16 13:32 ` Vivek Goyal
2009-04-16 13:32 ` [dm-devel] " Vivek Goyal
2009-04-15 4:37 ` 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 14:10 ` Vivek Goyal
2009-04-15 16:17 ` 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 14:11 ` [dm-devel] " Vivek Goyal
2009-04-16 20:24 ` Nauman Rafique
2009-04-20 8:29 ` Ryo Tsuruta
2009-04-20 8:29 ` [dm-devel] " 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 12:10 ` [dm-devel] " Ryo Tsuruta
2009-04-21 13:57 ` Mike Snitzer
2009-04-21 13:57 ` Mike Snitzer
2009-04-21 14:16 ` Vivek Goyal
2009-04-21 14:16 ` Vivek Goyal
2009-04-22 0:50 ` Li Zefan
2009-04-22 3:14 ` Ryo Tsuruta
2009-04-22 3:14 ` [dm-devel] " Ryo Tsuruta
2009-04-22 15:18 ` Mike Snitzer
2009-04-22 15:18 ` Mike Snitzer
2009-04-27 10:30 ` Ryo Tsuruta
2009-04-27 10:30 ` Ryo Tsuruta
2009-04-27 12:44 ` Ryo Tsuruta
2009-04-27 12:44 ` Ryo Tsuruta
2009-04-27 13:03 ` Mike Snitzer [this message]
2009-04-27 13:03 ` Mike Snitzer
2009-04-20 21:37 ` Vivek Goyal
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-16 20:57 ` Vivek Goyal
2009-04-17 2:11 ` Vivek Goyal
2009-04-17 2:11 ` Vivek Goyal
2009-04-17 2:28 ` 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=20090427130331.GB3872@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=ryov@valinux.co.jp \
--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 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.