Linus Torvalds writes: (Summary) wrote:
No.
No.
Stop this already./
Stop this already./
You're doing everthing wrong.
You're doing everthing wrong.
If the array has to describe *all* memory you will ever free, then you have already lost.
have already lost.
Just do it in chunks.
Just do it in chunks.
I don't want the VM code to even fill in that big of an array anyway - this all happens under the zone lock, and you're walking a list that is bad for caching anyway.
is bad for caching anyway.
So plan on an interface that allows _incremental_ freeing, because any plan that starts with "I worry that maybe two TERABYTES of memory isn't big enough" is so broken that it's laughable.
[...]
in multiple such max arrays (a list of them).No.
No.
Stop this already./
Stop this already./
You're doing everthing wrong.
You're doing everthing wrong.
If the array has to describe *all* memory you will ever free, then you have already lost.
have already lost.
Just do it in chunks.
Just do it in chunks.
I don't want the VM code to even fill in that big of an array anyway - this all happens under the zone lock, and you're walking a list that is bad for caching anyway.
is bad for caching anyway.
So plan on an interface that allows _incremental_ freeing, because any plan that starts with "I worry that maybe two TERABYTES of memory isn't big enough" is so broken that it's laughable.