[lkml]   [2007]   [Aug]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Apply memory policies to top two highest zones when highest zone is ZONE_MOVABLE

    > If correct, I would suggest merging the horrible hack for .23 then taking
    > it out when we merge "grouping pages by mobility". But what if we don't do
    > that merge?

    Or disable ZONE_MOVABLE until it is usable? I don't think we have the
    infrastructure to really use it anyways, so it shouldn't make too much difference
    in terms of features. And it's not that there is some sort of deadline
    around for it.

    Or mark it CONFIG_EXPERIMENTAL with a warning that it'll break NUMA. But disabling
    is probably better.

    Then for .24 or .25 a better solution can be developed.

    I would prefer that instead of merging bandaid horrible hacks -- they have
    a tendency to stay around.

    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: 2007-08-06 22:35    [W:0.022 / U:0.020 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site