[lkml]   [2010]   [Jul]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 0/14] Avoid overflowing of stack during page reclaim V3
    On Tue, 29 Jun 2010 12:34:34 +0100
    Mel Gorman <> wrote:

    > Here is V3 that depends again on flusher threads to do writeback in
    > direct reclaim rather than stack switching which is not something I'm
    > likely to get done before xfs/btrfs are ignoring writeback in mainline
    > (phd sucking up time).

    IMO, implemetning stack switching for this is not a good idea. We
    _already_ have a way of doing stack-switching. It's called

    The only reason I can see for implementing an in-place stack switch
    would be if schedule() is too expensive. And if we were to see
    excessive context-switch overheads in this code path (and we won't)
    then we should get in there and try to reduce the contect switch rate

     \ /
      Last update: 2010-07-02 21:37    [W:0.019 / U:2.664 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site