lkml.org 
[lkml]   [2014]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [PATCH 0/7] improve robustness on handling migratetype
    From
    2014/1/9 Michal Nazarewicz <mina86@mina86.com>:
    > On Thu, Jan 09 2014, Joonsoo Kim <iamjoonsoo.kim@lge.com> wrote:
    >> Third, there is the problem on buddy allocator. It doesn't consider
    >> migratetype when merging buddy, so pages from cma or isolate region can
    >> be moved to other migratetype freelist. It makes CMA failed over and over.
    >> To prevent it, the buddy allocator should consider migratetype if
    >> CMA/ISOLATE is enabled.
    >
    > There should never be situation where a CMA page shares a pageblock (or
    > a max-order page) with a non-CMA page though, so this should never be an
    > issue.

    Right... It never happens.
    When I ported CMA region reservation code to my own code for testing,
    I made a mistake. Sorry for noise.

    Thanks.


    \
     
     \ /
      Last update: 2014-01-09 16:01    [W:4.369 / U:0.176 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site