linux-kernel - Re: [patch v3]numa: add a sysctl to control interleave allocation granularity from each node to improve I/O performance

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:	Thu, 15 Dec 2011 09:27:51 +0800
From:	Shaohua Li <shaohua.li@...el.com>
To:	Andi Kleen <ak@...ux.intel.com>
Cc:	Christoph Lameter <cl@...ux.com>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jens Axboe <axboe@...nel.dk>,
	"lee.schermerhorn@...com" <lee.schermerhorn@...com>,
	David Rientjes <rientjes@...gle.com>
Subject: Re: [patch v3]numa: add a sysctl to control interleave allocation
 granularity from each node to improve I/O performance

On Thu, 2011-12-15 at 01:53 +0800, Andi Kleen wrote:
> > That's what I want to avoid letting each apps to explicitly do it, it's
> > a lot of burden.
> 
> Usually apps that set NUMA policy can change it. Most don't anyways.
> If it's just a script with numactl it's easily changed.
Hmm, why should apps set different granularity? the granularity change
is to speed up I/O, which should have the same value for all apps.

> > That's true only workload with heavy I/O wants this. but I don't expect
> > it will harm other workloads.
> 
> How do you know?
I can't imagine how it could harm. Some arches can use big pages, big
granularity should already been tested for years.

Thanks,
Shaohua

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