>What is the problem with free_before_allocate now?
There's no stability issue.
But the current fix is suboptimal. Suppose we have somebody that is
freeing memory in try_to_free_pages (so free_before_allocate is 1). Then
one task with a RSS of 1giga exits and release 1giga of memory. If
somebody will try to allocate memory at this point he will have to block
too, while there's 1 giga of memory free. Avoiding the block if
nr_free_pages > freepages.high as in 2.2.16 disables the logic so that's
not a viable solution.
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/