[lkml]   [2011]   [Jul]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [patch 4/5] mm: writeback: throttle __GFP_WRITE on per-zone dirty limits
    Hi Andi,

    On Tue, Jul 26, 2011 at 5:37 AM, Andi Kleen <> wrote:
    >> The global dirty limits are put in proportion to the respective zone's
    >> amount of dirtyable memory and the allocation denied when the limit of
    >> that zone is reached.
    >> Before the allocation fails, the allocator slowpath has a stage before
    >> compaction and reclaim, where the flusher threads are kicked and the
    >> allocator ultimately has to wait for writeback if still none of the
    >> zones has become eligible for allocation again in the meantime.
    > I don't really like this. It seems wrong to make memory
    > placement depend on dirtyness.
    > Just try to explain it to some system administrator or tuner: her
    > head will explode and for good reasons.
    > On the other hand I like doing round-robin in filemap by default
    > (I think that is what your patch essentially does)
    > We should have made  this default long ago. It avoids most of the
    > "IO fills up local node" problems people run into all the time.
    > So I would rather just change the default in filemap allocation.
    > That's also easy to explain.

    Just out of curiosity.
    Why do you want to consider only filemap allocation, not IO(ie,
    filemap + sys_[read/write]) allocation?

    Kind regards,
    Minchan Kim
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2011-07-26 01:43    [W:0.034 / U:79.448 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site