On Thu, 22 Nov 2007, Bron Gondwana wrote:
quoted text
> 
> This patch includes some code cleanup from Linus and a toggle in
> /proc/sys/vm/dirty_highmem which can be set to 1 to add the highmem
> back to the total available memory count.

Just to verify - can you confirm that this "just fixes it" for you?

I think this is the right approach to take, and seems very safe (ie people 
who know that their loads are ok can just set the flag), but I do want to 
verify that there was nothing else going on, and that you now see the same 
performance as you did in 2.6.16?

The other alternative, of course, would be to simply allow the dirty 
percentages to be > 100%, but that's just *odd* ;)

		Linus
-
unsubscribe notice
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/