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: <4A4BE64A.3050805@kernel.org>
Date:	Thu, 02 Jul 2009 07:42:18 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Christoph Lameter <cl@...ux-foundation.org>
CC:	Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, x86@...nel.org,
	linux-arch@...r.kernel.org, hpa@...or.com, tglx@...utronix.de
Subject: Re: [PATCHSET] percpu: generalize first chunk allocators and improve
 lpage NUMA support

Christoph Lameter wrote:
> On Wed, 1 Jul 2009, Andi Kleen wrote:
> 
>> And it's imho unclear if that is all worth it just to avoid
>> wasting some memory in the "256 possible CPUs" case (which
>> I doubt is particularly realistic anyways, at least I don't
>> know of any Hypervisor today that scales to 256 CPUs)
> 
> I basically agree. Its not worth it given the rare cases where this
> matters. It will be a lot of code with callbacks in each subsystem.
> 
> One of the motivations of working on revising the percpu handling for
> me was that we could get rid of these screwy callbacks that are rarely
> tested and cause all sorts of other issues with locking and serialization.

Hmmm.... yeah.  I have to agree that callbacks are nasty and requiring
all users to use callbacks wouldn't be very nice.  Once the current
dust settles down, I'll look around and see whether this can be solved
in some reasonable way.

Thanks.

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