I will go over the rest of the email later I just wanted to make this point clear because I suspect we are talking past each other. On Thu 24-05-18 16:04:38, David Hildenbrand wrote: [...] > The point I was making is: I cannot allocate 8MB/128MB using the buddy > allocator. All I want to do is manage the memory a virtio-mem device > provides as flexible as possible. I didn't mean to use the page allocator to isolate pages from it. We do have other means. Have a look at the page isolation framework and have a look how the current memory hotplug (ab)uses it. In short you mark the desired physical memory range as isolated (nobody can allocate from it) and then simply remove it from the page allocator. And you are done with it. Your particular range is gone, nobody will ever use it. If you mark those struct pages reserved then pfn walkers should already ignore them. If you keep those pages with ref count 0 then even hotplug should work seemlessly (I would have to double check). So all I am arguing is that whatever your driver wants to do can be handled without touching the hotplug code much. You would still need to add new ranges in the mem section units and manage on top of that. You need to do that anyway to keep track of what parts are in use or offlined anyway right? Now the mem sections. You have to do that anyway for memmaps. Our sparse memory model simply works in those units. Even if you make a part of that range unavailable then the section will still be there. Do I make at least some sense or I am completely missing your point? -- Michal Hocko SUSE Labs
