linux-kernel - Re: [PATCH 1/1] mm: add dirty

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 26 Nov 2007 09:53:17 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Bron Gondwana <brong@...tmail.fm>
cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Christian Kujau <lists@...dbynature.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	robm@...tmail.fm
Subject: Re: [PATCH 1/1] mm: add dirty_highmem option



On Thu, 22 Nov 2007, Bron Gondwana wrote:
> 
> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/