On Tue, 24 Jul 2018, Kirill A. Shutemov wrote: > > use_zero_page is currently a simple thp flag, meaning it rejects writes > > where val != !!val, so perhaps it would be best to overload it with > > additional options? I can imagine 0x2 defining persistent allocation so > > that the hzp is not freed when the refcount goes to 0 and 0x4 defining if > > the hzp should be per node. Implementing persistent allocation fixes our > > concern with it, so I'd like to start there. Comments? > > Why not a separate files? > That works as well. I'll write a patch for persistent allocation first to address our most immediate need.