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  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:	Wed, 28 Oct 2009 13:38:42 +0200
From:	Pekka Enberg <>
To:	Tejun Heo <>
Cc:	Ingo Molnar <>,
	FUJITA Tomonori <>,,,,,
	Andrew Morton <>,
	Yinghai Lu <>,
	Linus Torvalds <>,
	Peter Zijlstra <>,
	Vegard Nossum <>,
	"H. Peter Anvin" <>,
	Thomas Gleixner <>
Subject: Re: [PATCH 07/10] bootmem: add free_bootmem_late

Hi Tejun,

On Wed, Oct 28, 2009 at 10:00 AM, Tejun Heo <> wrote:
> ISTR an attempt to initialize the kmalloc allocator much earlier
> during boot such that it can completely replace the bootmem allocator,
> which would nicely remove all the complications although it may
> require the kmalloc allocator to go through more complex boot
> strapping steps.  I didn't follow how that went.  Did it prove to be
> unworkable?

We're doing it before scheduler init now but I haven't put any effort
into moving it earlier than that yet. I don't see any fundamental
reason we can't do that but the practical problem is that we're going
to affect architecture specific boot code which is really hard to

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists