linux-kernel - Re: [PATCH] x86: do not grow initial process stack so much

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: <487FD1D9.9020100@kernel.org>
Date:	Thu, 17 Jul 2008 16:12:25 -0700
From:	"H. Peter Anvin" <hpa@...nel.org>
To:	Denys Vlasenko <vda.linux@...glemail.com>
CC:	Ingo Molnar <mingo@...e.hu>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: do not grow initial process stack so much

Denys Vlasenko wrote:
> 
> I do not see, though, why this can be useful for x86. The pages
> are not mapped anyway, so accessing them still causes page faults.
> No speedup for, say, rapidly spawning processes which need ~60k
> of stack right away. They will still fault in kernel, right?
> 

They will fault in the kernel, but only to fill the page tables, so it 
would cut down on latency.

I do *NOT* believe we should make this an x86-only change.  If it should 
be architecture-dependent I'd rather find the architectures that do need it.

However, before changing this I really want to see some of the history 
about why it's that way in the first place.

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