<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Best results imho would be use lightly #ifdefed C and ignore OpenBSD.<BR>
Perhaps we should provide something for Modula-3, that is then portable to user threads.<BR>
<BR>
<BR>
The Win32 equivalent is "thread local storage", or, if you are picky and care "fiber local storage".<BR>
TlsAlloc <BR>
TlsGetValue <BR>
TlsSetValue <BR>
TlsFree <BR>
<BR>
<BR>
Search the web, you'll find the documentation right away.<BR>
<BR>
<BR>
There are also Fls functions. They aren't in XP and fibers are exceedingly rarely used.<BR>
Fiber local storage is thread local if fibers aren't in use.<BR>
That is, using FLS is like a "superset" of TLS. You can't go wrong by using it, except you need to handle the LoadLibrary/GetProcAddress to see if the functions are available or not.<BR>
<BR>
<BR>
For TLS (and FLS?), there is an array of 64 and an array of 1024, pointers. Each thread local is a pointer. You can heap allocate therein. Note that the heap allocation can fail. And Tls can be exhausted.<BR>
The maximum number of thread locals is 1088.<BR>
On older operating systems it is 64. <BR>
TlsGet/SetValue just index into the appropriate array.<BR>
<BR>
<BR>
If you are in an .exe, or a .dll that the .exe statically depends upon, or depend on Vista or newer, than __declspec(thread) is more convenient, faster, and I think has no limits. You just put that marker on your data and voila, the compiler, linker, and loader collaborate. (as well as the context switcher, which must be involved in both mechanisms).<BR>
<BR>
<BR>
That is __declspec(thread) does not work in .dlls that are loaded via LoadLibrary, prior to Vista.<BR>
This is a major downer, though decreasing in time now, as __declspec(thread) is so preferable.<BR>
<BR>
<BR>
Non-Win32 systems often have "__thread" that is equivalent ot __declspec(thread), probably without an equivalent dlopen limitation, but of varying efficiency -- really, read the spec, it is confusing, there are so many "models" for the linker/loader to worry about.<BR>
<BR>
<BR>
Current gcc emulates __thread in terms of "whatever" (tls or pthread) if there isn't anything better.<BR>
<BR>
<BR>
I did some experiments though and __thread didn't seem all that much faster, at least once you go to the worst of the "models".<BR>
"models" include like in the executable or a shared object, position-independent or not.<BR>
<BR>
<BR>
m3core uses pthread_getspecific/setspecific -- like for every occurence of "TRY" -- but those experiments were around having it use __thread if it is available.<BR>
Ultimately we just want to dramatically reduce the use of that specific data anyway -- by having a stack walker or using whatever the underlying native exception handling mechanism is..<BR>
<BR>
<BR>
There is surprisingly more to this subject. Imagine you have a few thread locals and you pack them together into a heap allocated struct/record.<BR>
It is tempting to think DllMain(THREAD_ATTACH) is the place to do the allocation. It is, but threads can be created before your .dll is loaded, and you won't get notifications for them. So you are still left having to do the allocation on-demand. You are still left with "failure points" on every access. <BR>
<BR>
<BR>
Thread locals are also "fragile", nearly as much so as globals.<BR>
Like, written when you don't realize and their value "lost".<BR>
<BR>
<BR>
What I mean, is, imagine this code:<BR>
<BR>
<BR>
f = fopen(...)<BR>
if (!f)<BR>
return errno;<BR>
<BR>
errno is a thread local on all modern systems.<BR>
Then imagine similar:<BR>
<BR>
<BR>
f = fopen(...)<BR>
if (!f)<BR>
return errno;<BR>
g = fopen(...)<BR>
if (!g)<BR>
{<BR>
fclose(f); /* preferably in a destructor or finally! */<BR>
return errno;<BR>
}<BR>
<BR>
<BR>
See the bug? fclose might have clobbered errno.<BR>
<BR>
<BR>
As well, accessing thread locals is always going to much slower than accessing a function local or parameter.<BR>
You really should try to avoid them.<BR>
<BR>
<BR>
- Jay<BR><BR><BR> <BR>
> From: darko@darko.org<BR>> Date: Mon, 13 Sep 2010 22:08:19 -0700<BR>> To: dragisha@m3w.org<BR>> CC: m3devel@elegosoft.com<BR>> Subject: Re: [M3devel] Per thread data<BR>> <BR>> I'm guessing that the pthread calls wouldn't be portable to Win32? Which is ok if there are similar calls for Win threads.<BR>> <BR>> <BR>> On 13/09/2010, at 9:57 PM, Dragiša Durić wrote:<BR>> <BR>> > Only "better" would be using same storage as for MyId... Access time<BR>> > would be same as for that value, and if you use MyId access time is<BR>> > access to TLS (thread local storage) plus your structure manipulation.<BR>> > IMO, some IntRefTbl is better idea than list.<BR>> > <BR>> > If you decide to use same storage, then it's pthread.getspecific and<BR>> > pthread.setspecific you are looking for.<BR>> > <BR>> > On Mon, 2010-09-13 at 21:14 -0700, Darko wrote:<BR>> >> I need to have certain data structures allocated on a per thread basis. Right now I'm thinking of using the thread id from ThreadF.MyId() to index a list. Is there a better, more portable way of allocating on a per-thread basis?<BR>> >> <BR>> >> Cheers,<BR>> >> Darko.<BR>> >> <BR>> > <BR>> > -- <BR>> > Dragiša Durić <dragisha@m3w.org><BR>> > <BR>> <BR> </body>
</html>