linux-kernel - Re: [RFC v2] percpu: Add a separate function to merge free areas

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 4 Dec 2014 15:45:34 -0500
From:	Tejun Heo <tj@...nel.org>
To:	Christoph Lameter <cl@...ux.com>
Cc:	Leonard Crestez <lcrestez@...acom.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Sorin Dumitru <sdumitru@...acom.com>
Subject: Re: [RFC v2] percpu: Add a separate function to merge free areas

Hello, Christoph.

On Thu, Dec 04, 2014 at 02:28:10PM -0600, Christoph Lameter wrote:
> Well this is not a common use case and that is not what the per cpu
> allocator was designed for. There is bound to be signifcant fragmentation
> with the current design. The design was for rare allocations when
> structures are initialized.

My unverified gut feeling is that fragmentation prolly is a lot less
of a problem for percpu allocator given that most percpu allocations
are fairly small.  On the other hand, we do wanna pack them tight as
percpu memory is really expensive space-wise.  I could be wrong tho.

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/