[lkml]   [2003]   [Dec]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: memory hotremove prototype, take 3

    > > > During hotunplug, you copy pages to new locaion. Would it simplify
    > > > code if you forced them to be swapped out, instead? [Yep, it would be
    > > > slower...]
    > >
    > > There are some pages that will have to be copied (e.g. pages that
    > > the user "mlock()d" should still be locked in their new location,
    > > same for hugetlbfs pages).

    And some pages which aren't associated with backing store like sysfs or
    ramdisk have to be, too.

    > Using kswapd is easy, but doesn't always work well. The patch
    > contains the code to ignore page accessed bits when kswapd is run on
    > disabled zones, but that's not enough for swapping out frequently used
    > pages.
    > In my patch, page copying, or "remapping", solves this problem by
    > blocking accesses to the page under operation.

    Thank you,
    Hirokazu Takahashi.
    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: 2005-03-22 13:59    [W:0.036 / U:85.320 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site