public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
	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, Balbir Singh <balbir@in.ibm.com>,
	vgoyal@redhat.com
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@valinux.co.jp>

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

  reply	other threads:[~2009-09-11 11:17 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 [this message]
2009-09-14  1:41   ` Ryo Tsuruta
2009-09-14  2:15 ` Mike Snitzer
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=20090911111632.GF4474@linux.vnet.ibm.com \
    --to=dhaval@linux.vnet.ibm.com \
    --cc=balbir@in.ibm.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=ryov@valinux.co.jp \
    --cc=vgoyal@redhat.com \
    --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