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]
Message-ID: <Pine.LNX.4.64.0612040900210.31485@schroedinger.engr.sgi.com>
Date:	Mon, 4 Dec 2006 09:03:59 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Linus Torvalds <torvalds@...l.org>
cc:	Andrew Morton <akpm@...l.org>, Aucoin@...ston.rr.com,
	"'Tim Schmielau'" <tim@...sik3.uni-rostock.de>,
	linux-kernel@...r.kernel.org, pj@....com
Subject: Re: la la la la ... swappiness

On Sun, 3 Dec 2006, Linus Torvalds wrote:

> Wouldn't it be much nicer to just lower the dirty-page limit?
> 
> 	echo 1 > /proc/sys/vm/dirty_background_ratio
> 	echo 2 > /proc/sys/vm/dirty_ratio

Dirty ratio cannot be set to less than 5%. See 
mm/page-writeback.c:get_dirty_limits().

> or something. Which we already discussed in another thread and almost 
> already decided we should lower the values for big-mem machines..

We also have an issue with cpusets. Dirty page throttling does not work in 
a cpuset if it is relatively small to the total memory on the system since 
we calculate the percentage of the total memory and not a percentage of 
the memory the process is allowed to use.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ