>With "right cases" here you mean waiting for IO completion while there is
>freeable pages around?
Yes.
>> I believe that the real problem of MAP_SHARED is
>> that we don't know anything about the state of the pages in MAP_SHARED
>> segment. We consider all them as clean without doing any write throttling
>> and we allow the VM to become fully dirty; while for good reasons in the
>> rest of the kernel we instead assume that there is a max percentage of the
>> RAM that could become dirty at the same time.
>
>Ok. Are you going to fix that?
There's first to fix the free_before_allocate thing properly but then I
can look into it of course.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/