From: Mike Snitzer <snitzer@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xensource.com,
ioband-devel@lists.sourceforge.net,
corsetproject@googlegroups.com, kunai@linux-foundation.jp,
osonoi@linux-foundation.jp
Subject: Re: IO controller Mini-Summit 2009
Date: Sun, 13 Sep 2009 22:15:10 -0400 [thread overview]
Message-ID: <20090914021509.GB4070@redhat.com> (raw)
In-Reply-To: <20090826.203251.260094379.ryov@valinux.co.jp>
On Wed, Aug 26 2009 at 7:32am -0400,
Ryo Tsuruta <ryov@valinux.co.jp> wrote:
> Hi All,
>
> As I have notified before, The 1st Linux IO controller Mini-Summit
> will be held in Tokyo Japan on Oct 17 -- day before the 9th Linux
> kernel summit. So I would like to propose the following topics for
> the mini-summit and discuss about them.
>
> - Multiple IO controller development projects
> - There are two activities for the development of IO controller,
> Vivek's io-controller and dm-ioband. Do we have to pick one of
> them to put into the mainline? How to advance the development?
This has been said by others before but: there is no reason the above
line of discussion can't happen on LKML et. al. (preferably now).
Deferring the discussion until Oct 17 guarantees that no solution would
be merged into 2.6.32. This would be quite unfortunate considering how
far Vivek's IO Controller has come. Aren't there also doubts about
whether the appropriate upstream people will be able to attend this
mini-summit?
Mike
next prev parent reply other threads:[~2009-09-14 2:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 11:32 IO controller Mini-Summit 2009 Ryo Tsuruta
2009-09-11 11:16 ` Dhaval Giani
2009-09-14 1:41 ` Ryo Tsuruta
2009-09-14 2:15 ` Mike Snitzer [this message]
2009-09-14 12:47 ` [dm-devel] " Ryo Tsuruta
-- strict thread matches above, loose matches on Subject: below --
2009-10-14 12:24 Ryo Tsuruta, Ryo Tsuruta
2009-10-14 17:55 ` Vivek Goyal
2009-10-15 0:39 ` Fernando Luis Vázquez Cao
2009-10-15 1:42 ` Takuya Yoshikawa
2009-10-15 2:35 ` Ryo Tsuruta
2009-10-15 1:59 ` Ryo Tsuruta
2009-10-15 11:20 ` 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=20090914021509.GB4070@redhat.com \
--to=snitzer@redhat.com \
--cc=containers@lists.linux-foundation.org \
--cc=corsetproject@googlegroups.com \
--cc=dm-devel@redhat.com \
--cc=ioband-devel@lists.sourceforge.net \
--cc=kunai@linux-foundation.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=osonoi@linux-foundation.jp \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.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