The intent is to fix them. Allowing more than 2G of dirty data to
float about seems unreasonable, and it pins buffer_heads.
But hey. The patch merely sets the initial value of /proc/sys/vm/dirty*,
and those things are writeable.
> Of course, "f**k highmem" is such
> a common refrain these days so that's probably falling on deaf ears.
On the contrary.
> AFAICT the OOM issues are largely a by-product of mempool allocations
> entering out_of_memory() when they have the perfectly reasonable
> alternative strategy of simply waiting for the mempool to refill.
I don't have enough RAM to reproduce this. Please send
call traces up from out_of_memory().
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/