Date: Tue, 15 Jan 2013 14:29:00 -0800 From: Alfred Perlstein <bright@mu.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Trent Nelson <trent@snakebite.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Getting the current thread ID without a syscall? Message-ID: <50F5D82C.7070400@mu.org> In-Reply-To: <20130115214332.GE2522@kib.kiev.ua> References: <20130115205403.GA52904@snakebite.org> <20130115211641.GC2522@kib.kiev.ua> <20130115213513.GA53047@snakebite.org> <20130115214332.GE2522@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/15/13 1:43 PM, Konstantin Belousov wrote: > On Tue, Jan 15, 2013 at 04:35:14PM -0500, Trent Nelson wrote: >> >> Luckily it's for an open source project (Python), so recompilation >> isn't a big deal. (I also check the intrinsic result versus the >> syscall result during startup to verify the same ID is returned, >> falling back to the syscall by default.) > For you, may be. For your users, it definitely will be a problem. > And worse, the problem will be blamed on the operating system and not > to the broken application. > Anything we can do to avoid this would be best. The reason is that we are still dealing with an "optimization" that perl did, it reached inside of the opaque struct FILE to "do nasty things". Now it is very difficult for us to fix "struct FILE". We are still paying for this years later. Any way we can make this a supported interface? -Alfred
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50F5D82C.7070400>