On Tue, Feb 22, 2011 at 07:03:58PM -0500, Vivek Goyal wrote:
I think we should accept to have an inode granularity. We could redesign
the writeback code to work per-cgroup / per-page, etc. but that would
add a huge overhead. The limit of inode granularity could be an
acceptable tradeoff,
Agreed. Granularity of per inode level might be accetable in many
cases. Again, I am worried faster group getting stuck behind slower
group.
I am wondering if we are trying to solve the problem of ASYNC write
throttling
at wrong layer. Should ASYNC IO be throttled before we allow
On Wed, Feb 23, 2011 at 10:23:54AM -0500, Vivek Goyal wrote:
Agreed. Granularity of per inode level might be accetable in many
cases. Again, I am worried faster group getting stuck behind slower
group.
I am wondering if we are trying to solve the problem of ASYNC write
On Thu, Feb 24, 2011 at 12:14:11AM +0100, Andrea Righi wrote:
On Wed, Feb 23, 2011 at 10:23:54AM -0500, Vivek Goyal wrote:
Agreed. Granularity of per inode level might be accetable in many
cases. Again, I am worried faster group getting stuck behind slower
group.
I am
On Wed, 23 Feb 2011 19:10:33 -0500
Vivek Goyal vgo...@redhat.com wrote:
On Thu, Feb 24, 2011 at 12:14:11AM +0100, Andrea Righi wrote:
On Wed, Feb 23, 2011 at 10:23:54AM -0500, Vivek Goyal wrote:
Agreed. Granularity of per inode level might be accetable in many
cases. Again, I am
On Wed, Feb 23, 2011 at 4:40 PM, KAMEZAWA Hiroyuki
kamezawa.hir...@jp.fujitsu.com wrote:
On Wed, 23 Feb 2011 19:10:33 -0500
Vivek Goyal vgo...@redhat.com wrote:
On Thu, Feb 24, 2011 at 12:14:11AM +0100, Andrea Righi wrote:
On Wed, Feb 23, 2011 at 10:23:54AM -0500, Vivek Goyal wrote:
* Andrea Righi ari...@develer.com [2011-02-22 18:12:51]:
Currently the blkio.throttle controller only support synchronous IO requests.
This means that we always look at the current task to identify the owner of
each IO request.
However dirty pages in the page cache can be wrote to disk
On Tue, Feb 22, 2011 at 06:12:51PM +0100, Andrea Righi wrote:
Currently the blkio.throttle controller only support synchronous IO requests.
This means that we always look at the current task to identify the owner of
each IO request.
However dirty pages in the page cache can be wrote to disk
On Tue, Feb 22, 2011 at 02:34:03PM -0500, Vivek Goyal wrote:
On Tue, Feb 22, 2011 at 06:12:51PM +0100, Andrea Righi wrote:
Currently the blkio.throttle controller only support synchronous IO
requests.
This means that we always look at the current task to identify the owner
of
each IO
On Tue, Feb 22, 2011 at 11:41:41PM +0100, Andrea Righi wrote:
On Tue, Feb 22, 2011 at 02:34:03PM -0500, Vivek Goyal wrote:
On Tue, Feb 22, 2011 at 06:12:51PM +0100, Andrea Righi wrote:
Currently the blkio.throttle controller only support synchronous IO
requests.
This means that we
10 matches
Mail list logo
