linux-kernel - Re: x86: 4kstacks default

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]

Date:	Mon, 21 Apr 2008 02:48:53 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	Bernd Eckenfels <ecki@...a.inka.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: x86: 4kstacks default

Bernd Eckenfels wrote:
> A question along this line. Why is the Userspace Thread bound to a
> Kernel-Space Stack at all? I could imagine a solution like Stack Pools
> assigned only of a Thread enters kernel space, or something like this?
>
>   

The vast majority of threads are sleeping (with a stack footprint in the 
kernel).  If you have an N-way system, at most N threads can be in 
userspace at any given moment.

You could multiplex several userspace threads on one kernel thread (the 
M:N model), but it gets fairly complex.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

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