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  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:	Wed, 27 Feb 2008 14:00:42 +0900
From:	KAMEZAWA Hiroyuki <>
To:	KOSAKI Motohiro <>
Cc:, Peter Zijlstra <>,,,
	Rik van Riel <>,
	Lee Schermerhorn <>,
	Nick Piggin <>
Subject: Re: [RFC][PATCH] page reclaim throttle take2

On Wed, 27 Feb 2008 13:45:18 +0900
KOSAKI Motohiro <> wrote:

> Hi
> > One more thing, I would request you to add default heuristics (number of
> > reclaimers), based on the number of cpus in the system. Letting people tuning it
> > is fine, but defaults should be related to number of cpus, nodes and zones on
> > the system. Zones can be reaped in parallel per node and cpus allow threads to
> > run in parallel. So please use that to come up with good defaults, instead of a
> > number like "3".
> I don't think so.
> all modern many cpu machine stand on NUMA.
> it mean following,
>  - if cpu increases, then zone increases, too.
> if default value increase by #cpus, lock contension dramatically increase
> on large numa.
> Have I overlooked anything?
How about adding something like..
default 3
depends on DEBUG
  This value determines the number of threads which can do page reclaim
  in a zone simultaneously. If this is too big, performance under heavy memory
  pressure will decrease.
  If unsure, use default.

Then, you can get performance reports from people interested in this
feature in test cycle.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists