[lkml]   [2009]   [Oct]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subject[PATCH 0/2] Reduce number of GFP_ATOMIC allocation failures
    The following two patches against 2.6.32-rc4 should reduce allocation
    failure reports for GFP_ATOMIC allocations that have being cropping up
    since 2.6.31-rc1.

    I believe these are candidates for -stable as they address issues in the
    following commit introduced in the v2.6.30..v2.6.31-rc1 window

    11e33f6 page allocator: break up the allocator entry point into fast and slow paths

    The patch should not have made functional changes but at least two slipped
    by. The first patch wakes kswapd up each time after OOM-killing has been
    considered. This can be important to high-order allocations where kswapd
    needs to reclaim at a higher order. The second patch corrects a problem
    whereby a process that is exiting and making a __GFP_NOFAIL allocation can
    ignore watermarks.

    These patches in combination should help reduce the number of GFP_ATOMIC
    failures in the following bug.

    [Bug #14141] order 2 page allocation failures in iwlagn

    However, this bug should not yet be closed as there are still problems in
    the driver itself that increase the number of GFP_ATOMIC allocations that bug.

    The patches should also help the following bugs as well and testing there
    would be appreciated.

    [Bug #14265] ifconfig: page allocation failure. order:5, mode:0x8020 w/ e100

    It might also have helped the following bug although that driver has already
    been fixed by not making high-order atomic allocations.

    [Bug #14016] mm/ipw2200 regression

    mm/page_alloc.c | 5 +++--
    1 files changed, 3 insertions(+), 2 deletions(-)

     \ /
      Last update: 2009-10-16 12:41    [W:0.028 / U:0.812 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site