Date: Mon, 30 May 2005 09:38:21 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Suleiman Souhlal <ssouhlal@FreeBSD.org> Cc: Robert Watson <ratson@FreeBSD.org>, arch@FreeBSD.org Subject: Re: [PATCH] Stackgap Message-ID: <20050530093629.K52379@fledge.watson.org> In-Reply-To: <CBB6990A-8E1B-43CF-B8B3-61B9D601968D@FreeBSD.org> References: <CBB6990A-8E1B-43CF-B8B3-61B9D601968D@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 29 May 2005, Suleiman Souhlal wrote: >> In the past, substantial performance hits have been measured due to poor >> stack alignment. Specifically, in combination with less optimal compiler >> behavior, the results have been pretty nasty. Have you tried >> micro-benchmarking a series of runs with this stack offset randomness using >> floating point on stack arguments to see if there's a measurable cost to >> moving the stack around? Hopefull if all is well, there will be little or >> no difference, but a small error here could result in a substantial >> performance hit... > > I've modified the patch to make sure that the random offset is always > correctly aligned.. Do you think it would be safe to commit it (maybe > having the stackgap off by default)? Have you had a chance to run any micro-benchmarks to confirm all is well? Also, I thought Poul-Henning's question about the degree of entropy here was interesting -- what's the actual scope of possible values? Are we talking about only a small number of offsets (16) or something much larger? I'm not opposed to it being merged as long as (a) we know it doesn't hurt us, and (b) it actually does help us. Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050530093629.K52379>