Re: [PATCH][5/?] count writeback pages in nr_scanned

From: Nick Piggin (nickpiggin_at_yahoo.com.au)
Date: 01/06/05

  • Next message: Francois Romieu: "Re: 2.6.10 TCP troubles"
    Date:	Thu, 06 Jan 2005 10:51:34 +1100
    To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
    
    

    Marcelo Tosatti wrote:
    >>The caller would need to wait on all the zones which can satisfy the
    >>caller's allocation request. A bit messy, although not rocket science.
    >>One would have to be careful to avoid additional CPU consumption due to
    >>delivery of multiple wakeups at each I/O completion.
    >>
    >>We should be able to demonstrate that such a change really fixes some
    >>problem though. Otherwise, why bother?
    >
    >
    > Agreed. The current scheme works well enough, we dont have spurious OOM kills
    > anymore, which is the only "problem" such change ought to fix.
    >
    > You might have performance increase in some situations I believe (because you
    > have perzone waitqueues), but I agree its does not seem to be worth the
    > trouble.

    I think what Andrea is worried about is that blk_congestion_wait is
    fairly vague, and can be a source of instability in the scanning
    implementation.

    For example, if you have a heavy IO workload that is saturating your
    disks, blk_congestion_wait may do the right thing and sleep until
    they become uncongested and writeout can continue.

    But at 2:00 am, when your backup job is trickling writes into another
    block device, blk_congestion_wait returns much earlier, and before
    many pages have been cleaned.

    Bad example? Yeah maybe, but I think this is what Andrea is getting
    at. Would it be a problem to replace those blk_congestion_waits with
    unconditional io_schedule_timeout()s? That would be the dumb-but-more
    -deterministic solution.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Francois Romieu: "Re: 2.6.10 TCP troubles"

    Relevant Pages

    • Re: nr_free_buffer_pages 2.4.23pre4
      ... it will remove a not necessary branch that also generates ... > Please apply this cleanup patch on top of the one above. ... Andrea ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: per-process shared information
      ... >> Hi Andrea! ... >> No useful comments on the statm reporting issue. ... >> We need to throttle more, on page reclaiming progress I think. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] fix spurious OOM kills
      ... The first stacktrace is from my patch. ... The second trace is ... as the allocation request now returns ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Configurable OOM killer Re: old oom-vm for 2.4.32 (was oom killer in 2.4.23)
      ... > The following patch makes OOM killer configurable (its the same as the ... > I hope the Configure.help entry is clear enough. ... As Andrea has pointed out earlier, a yieldafter out_of_memoryis safe and should be added too. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.4.22pre7aa1: unresolved in sk98lin
      ... >> Hi Andrea, ... I don't know who posted it originally though, Andrew ... send the line "unsubscribe linux-kernel" in ... More majordomo info at http://vger.kernel.org/majordomo-info.html ...
      (Linux-Kernel)