Re: ZONE_NORMAL vs. ZONE_MOVABLE

2017-03-30 Thread Vlastimil Babka
On 03/20/2017 07:33 AM, Joonsoo Kim wrote: >> The fact sticky movable pageblocks aren't ideal for CMA doesn't mean >> they're not ideal for memory hotunplug though. >> >> With CMA there's no point in having the sticky movable pageblocks >> scattered around and it's purely a misfeature to use sticky

Re: ZONE_NORMAL vs. ZONE_MOVABLE

2017-03-19 Thread Joonsoo Kim
2017-03-17 4:01 GMT+09:00 Andrea Arcangeli : > Hello Joonsoo, Hello, Andrea. > On Thu, Mar 16, 2017 at 02:31:22PM +0900, Joonsoo Kim wrote: >> I don't follow up previous discussion so please let me know if I miss >> something. I'd just like to mention about sticky pageblocks. > > The interesting

Re: ZONE_NORMAL vs. ZONE_MOVABLE

2017-03-17 Thread Igor Mammedov
On Thu, 16 Mar 2017 20:01:25 +0100 Andrea Arcangeli wrote: [...] > If we can make zone overlap work with a 100% overlap across the whole > node that would be a fine alternative, the zoneinfo.py output will > look weird, but if that's the only downside it's no big deal. With > sticky movable pageb

Re: ZONE_NORMAL vs. ZONE_MOVABLE

2017-03-16 Thread Andrea Arcangeli
Hello Joonsoo, On Thu, Mar 16, 2017 at 02:31:22PM +0900, Joonsoo Kim wrote: > I don't follow up previous discussion so please let me know if I miss > something. I'd just like to mention about sticky pageblocks. The interesting part of the previous discussion relevant for the sticky movable pagebl

Re: ZONE_NORMAL vs. ZONE_MOVABLE

2017-03-15 Thread Joonsoo Kim
On Wed, Mar 15, 2017 at 05:37:29PM +0100, Andrea Arcangeli wrote: > On Wed, Mar 15, 2017 at 02:11:40PM +0100, Michal Hocko wrote: > > OK, I see now. I am afraid there is quite a lot of code which expects > > that zones do not overlap. We can have holes in zones but not different > > zones interleav

Re: ZONE_NORMAL vs. ZONE_MOVABLE

2017-03-15 Thread Andrea Arcangeli
On Wed, Mar 15, 2017 at 02:11:40PM +0100, Michal Hocko wrote: > OK, I see now. I am afraid there is quite a lot of code which expects > that zones do not overlap. We can have holes in zones but not different > zones interleaving. Probably something which could be addressed but far > from trivial IM

Re: ZONE_NORMAL vs. ZONE_MOVABLE

2017-03-15 Thread Michal Hocko
On Wed 15-03-17 13:53:09, Vitaly Kuznetsov wrote: > Michal Hocko writes: > > > On Wed 15-03-17 11:48:37, Vitaly Kuznetsov wrote: [...] > >> What actually stops us from having the following approach: > >> 1) Everything is added to MOVABLE > >> 2) When we're out of memory for kernel allocations in

Re: ZONE_NORMAL vs. ZONE_MOVABLE

2017-03-15 Thread Vitaly Kuznetsov
Michal Hocko writes: > On Wed 15-03-17 11:48:37, Vitaly Kuznetsov wrote: >> Michal Hocko writes: > [...] >> Speaking about long term approach, > > Not really related to the patch but ok (I hope this will not distract > from the original intention here)... > Yes, not directly related to your pat

ZONE_NORMAL vs. ZONE_MOVABLE (was: Re: [RFC PATCH] rework memory hotplug onlining)

2017-03-15 Thread Michal Hocko
On Wed 15-03-17 11:48:37, Vitaly Kuznetsov wrote: > Michal Hocko writes: [...] > Speaking about long term approach, Not really related to the patch but ok (I hope this will not distract from the original intention here)... > (I'm not really familiar with the history of memory zones code so plea