Getting the current thread ID without a syscall?

Alfred Perlstein bright at mu.org
Tue Jan 15 22:29:11 UTC 2013


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




More information about the freebsd-hackers mailing list