linux-kernel - Re: [PATCH -mm] clean up duplicated alloc/free_thread

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: <18500.59345.230174.727316@cargo.ozlabs.ibm.com>
Date:	Tue, 3 Jun 2008 16:42:25 +1000
From:	Paul Mackerras <paulus@...ba.org>
To:	"Pekka Enberg" <penberg@...helsinki.fi>
Cc:	"FUJITA Tomonori" <fujita.tomonori@....ntt.co.jp>,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: [PATCH -mm] clean up duplicated alloc/free_thread_info

Pekka Enberg writes:

> Yeah, I too have wondered why some architectures use kmalloc() whereas
> others use the page allocator. Is THREAD_SIZE significantly smaller
> than PAGE_SIZE for those?

64-bit powerpc uses 16k kernel stacks and either 4k or 64k page size.
If the page size is 64k then we don't want to allocate a whole page
for a kernel stack.

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