From: Dhaval Giani <dhaval-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Ryo Tsuruta <ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
Cc: xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
ioband-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
corsetproject-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
kunai-de/tnXTf+JLsfHDXvbKv3Xf5DAMn2ifp@public.gmane.org,
osonoi-de/tnXTf+JLsfHDXvbKv3Xf5DAMn2ifp@public.gmane.org
Subject: Re: IO controller Mini-Summit 2009
Date: Fri, 11 Sep 2009 16:46:32 +0530 [thread overview]
Message-ID: <20090911111632.GF4474@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090826.203251.260094379.ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
On Wed, Aug 26, 2009 at 08:32:51PM +0900, Ryo Tsuruta 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?
>
> - Extensions of struct bio
> - Make a bio point to the io_context of a process which creates the
> I/O request. This allows to pass the IO scheduling class and
> priority information to IO controller even if the IO is submitted
> by another process which does not create the request, such as a
> worker thread.
> - Add a new flag to struct bio to identify the bio as urgent. This
> gives IO controller a chance to handle the bio as high priority.
> This flag should be set if the bio is created for the page-out
> operation.
>
> - I/O tracking and charging policy
> - Which process, a page-requesting process or a page-returning
> process, should be charged for the I/O caused by page reclaim?
> We should consider two cases where the IO flushes anonymous pages
> and file mapped pages.
>
> I think this is a good opportunity to meet face-to-face to discuss
> about IO controller development. I would like to many developers to
> join this mini-summit. Please visit the following URL for more
> information about the mini-summit.
> http://apps.sourceforge.net/trac/ioband/wiki/iosummit
> If you would like to join the mini-summit, please e-mail to me or post
> on the wiki page,
> (You need an account on SourceForge.net to edit the wiki page.)
>
> All comments, questions, suggestions and anything else are appreciated.
>
Hi Ryo,
Would you be having a remote dial-in for folks who cannot attend in
person?
thanks,
--
regards,
Dhaval
next parent reply other threads:[~2009-09-11 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090826.203251.260094379.ryov@valinux.co.jp>
[not found] ` <20090826.203251.260094379.ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
2009-09-11 11:16 ` Dhaval Giani [this message]
[not found] ` <20090911111632.GF4474-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2009-09-14 1:41 ` IO controller Mini-Summit 2009 Ryo Tsuruta
2009-09-14 2:15 ` Mike Snitzer
[not found] ` <20090914021509.GB4070@redhat.com>
[not found] ` <20090914021509.GB4070-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-09-14 12:47 ` [dm-devel] " Ryo Tsuruta
[not found] <20091014.212444.179938286.ryov@valinux.co.jp>
[not found] ` <20091014.212444.179938286.ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
2009-10-14 17:55 ` Vivek Goyal
2009-10-19 7:58 ` Ryo Tsuruta
[not found] ` <20091014175521.GG3528@redhat.com>
[not found] ` <4AD66F28.9030607@oss.ntt.co.jp>
[not found] ` <4AD66F28.9030607-gVGce1chcLdL9jVzuh4AOg@public.gmane.org>
2009-10-15 1:42 ` Takuya Yoshikawa
[not found] ` <4AD67DFB.60402@oss.ntt.co.jp>
[not found] ` <4AD67DFB.60402-gVGce1chcLdL9jVzuh4AOg@public.gmane.org>
2009-10-15 2:35 ` Ryo Tsuruta
[not found] ` <20091014175521.GG3528-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-10-15 0:39 ` Fernando Luis Vázquez Cao
2009-10-15 1:59 ` Ryo Tsuruta
[not found] ` <20091015.105902.70196131.ryov@valinux.co.jp>
[not found] ` <20091015.105902.70196131.ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
2009-10-15 11:20 ` Ryo Tsuruta
2009-10-14 12:24 Ryo Tsuruta, Ryo Tsuruta
-- strict thread matches above, loose matches on Subject: below --
2009-08-26 11: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=20090911111632.GF4474@linux.vnet.ibm.com \
--to=dhaval-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=corsetproject-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=ioband-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kunai-de/tnXTf+JLsfHDXvbKv3Xf5DAMn2ifp@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=osonoi-de/tnXTf+JLsfHDXvbKv3Xf5DAMn2ifp@public.gmane.org \
--cc=ryov-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org \
--cc=virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
/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