linux-kernel - Re: Slab infrastructure for bulk object allocation and freeing V2

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] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.11.1504061325350.27939@gentwo.org>
Date:	Mon, 6 Apr 2015 13:27:07 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Jesper Dangaard Brouer <brouer@...hat.com>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	akpm@...uxfoundation.org, Pekka Enberg <penberg@...nel.org>,
	iamjoonsoo@....com
Subject: Re: Slab infrastructure for bulk object allocation and freeing V2

On Thu, 2 Apr 2015, Andrew Morton wrote:

> hm, OK.  The per-allocator wrappers could be made static inline in .h
> if that makes sense.

The allocators will add code to the "per-allocator wrappers". Inlining
that would be bad. Basicalkly the "wrapper" is the skeleon to which
optimizations can be added while keeping the call to the generic
implementaiton if the allocator has to punt for some reason.

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