lkml.org 
[lkml]   [2012]   [Apr]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] writeback and cgroup
Hello, Vivek.

On Wed, Apr 04, 2012 at 04:32:39PM -0400, Vivek Goyal wrote:
> > Let's say we have iops/bps limitation applied on top of proportional IO
> > distribution
>
> We already do that. First IO is subjected to throttling limit and only
> then it is passed to the elevator to do the proportional IO. So throttling
> is already stacked on top of proportional IO. The only question is
> should it be pushed to even higher layers or not.

Yeah, I know we already can do that. I was trying to give an example
of non-trivial IO limit configuration.

> So split model is definitely confusing. Anyway, block layer will not
> apply the limits again as flusher IO will go in root cgroup which
> generally goes to root which is unthrottled generally. Or flusher
> could mark the bios with a flag saying "do not throttle" bios again as
> these have been throttled already. So throttling again is probably not
> an issue.
>
> In summary, agreed that split is confusing and it fills a gap existing
> today.

It's not only confusing. It's broken. So, what you're saying is that
there's no provision to orchestrate between buffered writes and other
types of IOs. So, it would essentially work as if there are two
separate controls controlling each of two heavily interacting parts
with no designed provision between them. What the....
--
tejun


\
 
 \ /
  Last update: 2012-04-05 01:05    [from the cache]
©2003-2011 Jasper Spaans