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: <m2d2324vxc.wl@sfc.wide.ad.jp>
Date:	Sat, 18 Apr 2015 00:27:27 +0900
From:	Hajime Tazaki <tazaki@....wide.ad.jp>
To:	richard@....at
Cc:	cl@...ux.com, linux-arch@...r.kernel.org, arnd@...db.de,
	corbet@....net, penberg@...nel.org, rientjes@...gle.com,
	iamjoonsoo.kim@....com, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
	netdev@...r.kernel.org, linux-mm@...ck.org, jdike@...toit.com,
	rusty@...tcorp.com.au, upa@...ena.net, christoph.paasch@...il.com,
	mathieu.lacage@...il.com, libos-nuse@...glegroups.com
Subject: Re: [RFC PATCH v2 02/11] slab: add private memory allocator header for arch/lib


At Fri, 17 Apr 2015 17:08:22 +0200,
Richard Weinberger wrote:

> >>>> add header includion for CONFIG_LIB to wrap kmalloc and co. This will
> >>>> bring malloc(3) based allocator used by arch/lib.
> >>>
> >>> Maybe add another allocator insteadl? SLLB which implements memory
> >>> management using malloc()?
> >>
> >> Yeah, that's a good idea.
> > 
> > first, my bad, I should be more precise on the commit message.
> > 
> > the patch with 04/11 patch is used _not_ only malloc(3) but
> > also any allocator registered by our entry API, lib_init().
> > 
> > for NUSE case, we use malloc(3) but for DCE (ns-3) case, we
> > use our own allocator, which manages the (virtual) process
> > running on network simulator.
> > 
> > if these externally configurable memory allocator are point
> > of interest in Linux kernel, maybe adding another allocator
> > into mm/ is interesting but I'm not sure. what do you think ?
> 
> This is the idea behind SLLB.
> 
> > btw, what does stand for SLLB ? (just curious)
> 
> SLUB is the unqueued SLAB and SLLB is the library SLAB. :D

thanks.
I will be back with SLLB and give v3 patches soon.

-- Hajime

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