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:	Tue, 27 Jan 2009 13:47:47 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	cl@...ux-foundation.org
Cc:	tj@...nel.org, rusty@...tcorp.com.au, mingo@...e.hu,
	herbert@...dor.apana.org.au, akpm@...ux-foundation.org,
	hpa@...or.com, brgerst@...il.com, ebiederm@...ssion.com,
	travis@....com, linux-kernel@...r.kernel.org, steiner@....com,
	hugh@...itas.com, netdev@...r.kernel.org,
	mathieu.desnoyers@...ymtl.ca
Subject: Re: [PATCH] percpu: add optimized generic percpu accessors

From: Christoph Lameter <cl@...ux-foundation.org>
Date: Tue, 27 Jan 2009 15:08:57 -0500 (EST)

> On Tue, 27 Jan 2009, Tejun Heo wrote:
> 
> > > later). That's because they use TLB tricks for a static 64k per-cpu
> > > area, but this doesn't scale.  That might not be vital: abandoning
> > > that trick will mean they can't optimise read_percpu/read_percpu_var
> > > etc as much.
> 
> Why wont it scale? this is a separate TLB entry for each processor.

The IA64 per-cpu TLB entry only covers 64k which makes use of it for
dynamic per-cpu stuff out of the question.  That's why it "doesn't
scale"
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ