Dave Hansen wrote:in this case no memory fractions accounting is possible :/
My main thought is that _everybody_ is going to have to live with the
entry in the 'struct page'. Distros ship one kernel for everybody, and
the cost will be paid by those not even using any kind of resource
control or containers.
Every userspace or page cache page will be in an object
though. Could we do the pointer on a per object (mapping,
anon vma, ...) basis?
Kernel pages are not using all of their struct page entries,yeah, we can. probably mapping.
so we could overload a field.
It all depends on how much we really care about not growingso what is your opinion?
struct page :)