Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > Would arch maintainers please look at fixing this in their architectures
> > instead? Make TASK_SIZE be the maximum size a process VM can have.
>
> The problem is that compat flexmmap depends on it. I actually dropped
> flexmmap
> again, but the x86-64 flexmmap which will be merged at some point again
> had a x86-64 change to switch to variable TASK_SIZE.
TASK_SIZE is a property of the mm_struct, is it not? Why can't add
mm_struct.task_size and kill off TASK_SIZE altogether? And MM_VM_SIZE?
Stuff like ia64's
#define TASK_SIZE (current->thread.task_size)
just seems dead wrong to me, in the case where a random /proc reader is the
last one left holding a reference to the mm.
Paul's patch seems disjoint from the above - it adds task_size.max_addr
which records the highest virtual address which the mm has mapped. Nice
for optimising various teardown things, but not suitable for TASK_SIZE
elimination.
