linux-kernel - Re: [PATCH v3 21/21] mm: zone lru vectors interleaving

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: <20120223162111.GA4713@one.firstfloor.org>
Date:	Thu, 23 Feb 2012 17:21:11 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Konstantin Khlebnikov <khlebnikov@...nvz.org>
Cc:	Hugh Dickins <hughd@...gle.com>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, Johannes Weiner <hannes@...xchg.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Andi Kleen <andi@...stfloor.org>, tim.c.chen@...ux.intel.com
Subject: Re: [PATCH v3 21/21] mm: zone lru vectors interleaving

> +config PAGE_LRU_SPLIT
> +	int "Memory lru lists per zone"
> +	default	4 if EXPERIMENTAL && SPARSEMEM_VMEMMAP
> +	default 1
> +	help
> +	  The number of lru lists in each memory zone for interleaving.
> +	  Allows to redeuce lru_lock contention, but adds some overhead.
> +	  Without SPARSEMEM_VMEMMAP might be costly. "1" means no split.

Could you turn those two numbers into a boot option? Compile time 
parameters are nasty to use.

I suppose it's ok to have an upper limit.

> +
> +config PAGE_LRU_INTERLEAVING
> +	int "Memory lru lists interleaving page-order"
> +	default	12
> +	help
> +	  Page order for lru lists interleaving. By default 12 (16Mb).
> +	  Must be greater than huge-page order.
> +	  With CONFIG_PAGE_LRU_SPLIT=1 has no effect.

-Andi
--
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/