青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品

無(wú)我

讓內(nèi)心永遠(yuǎn)燃燒著偉大的光明的精神之火!
靈活的思考,嚴(yán)謹(jǐn)?shù)膶?shí)現(xiàn)
豪邁的氣魄、頑強(qiáng)的意志和周全的思考

【轉(zhuǎn)】Thread Local Storage - The C++ Way

http://www.codeproject.com/Articles/8113/Thread-Local-Storage-The-C-Way

 

Introduction

Global data, while usually considered poor design, nevertheless often is a useful means to preserve state between related function calls. When it comes to using threads, the issue unfortuantely is complicated by the fact that some access synchronisation is needed, to avoid that more than one thread will modify the data.

There are times when you will want to have a globally visible object, while still having the data content accessible only to the calling thread, without holding off other threads that contend for the "same" global object. This is where thread local storage (TLS) comes in. TLS is something the operating system / threading subsystem provides, and by its very nature is rather low level.

From a globally visible object (in C++) you expect that its constructors are getting called before you enter "main", and that it is disposed properly, after you exit from "main". Consequently one would expect a thread local "global" object beeing constructed, when a thread starts up, and beeing destroyed when the thread exits. But this is not the case! Using the native API one can only have TLS that needs neither code to construct nor code to destruct.

While at first glance this is somewhat disappointing, there are reasons, not to automatically instantiate all these objects on every thread creation. A clean solution to this problem is presented e.g. in the library. Also the standard "pthread" C library addresses this problem properly. But when you need to use the native windows threading API, or need to write a library that, while making use of TLS, has no control over the threading API the client code is using, you are apparently lost.

Fortunately this is not true, and this is the topic of this article. The Windows Portable Executable (PE) format provides for support of TLS-Callbacks. Altough the documentation is hard to read, it can be done with current compilers i.e. MSVC 6.0,7.1,... Since noone else seemingly was using this feature before, and not even the C runtime library (CRT) is making use of it, you should be a little careful and watch out for undesired behaviour. Having said, that the CRT does not use it, does not mean it does not implement it. Unfortunately there is a small bug present in the MSVC 6.0 implementation, that is also worked-around by my code.

If it turns out, that the concepts, presented in this article, prove to be workable in "real life", I would be glad if this article has helped to remove some dust from this topic and make it usable for a broader range of applications. I could e.g. think of a generalized atexit_thread function that makes use of the concepts presented here.

Before going to explain the gory details, I want to mention Aaron W. LaFramboise who made me aware of the existence of the TLS-Callback mechanism.

Using the code

If you are using the precompiled binaries, you simply will need to copy the *.lib files to a convenient directory where your compiler usually will find libraries. So you will copy the files from the include directory to a directory where your compiler searches for includes. Alternatively you may simply copy the files to your project directory.

The following is a simple demonstration of usage, to get you started.

#include <process.h>
// first include the header file
#include <tls.h>

// this is your class
struct A {
    A() : n(42) {
    }
    ~A() {
    }
    int the_answer_is() {
        int m = n;
        n = 0;
        return m;
    }
int n;
};        

// now define a tls wrapper of class A
tls_ptr<A> pA;

// this is the threaded procedure
void  run(void*)
{
    // instantiate a new "A"
    pA.reset(new A);

    // access the tls-object    
    ans = pA->the_answer_is();

    // note, that we do not need to deallocate
    // the object. This is getting done automagically
    // when the thread exits.
}

int main(int argc, char* argv[])
{
    // the main thread also gets a local copy of the tls.
    pA.reset(new A);

    // start the thread
    _beginthread(&run, 0, 0);

    // call into the main threads version
    pA->the_answer_is();

    // the "run" thread should have ended when we
    // are exiting.
    Sleep(10000);
    
    // again we do not need to free our tls object.
    // this is comparable in behaviour to objects
    // at global scope.
    return 0;
}

While at first glance it might appear natural that the tls-objects should not be wrapped as pointers, in fact it is not. While the objects are globally visible, they are still "delegates" that forward to a thread local copy. The natural way in C++ to express delegation is a pointer object. (The technical reason of course is, that you cannot overload the "." operator but "->" can be overloaded.)

You can use this mechanism when building a "*.exe" file of course, but you also can use it when building a "*.dll" image. However when you are planning to load your DLL by LoadLibary() you should define the macro TLS_ALLOC when building your DLL. This is not necessary when using your DLL by means of an import library. A similar restriction applies when delay-loading your DLL. Please consult your compiler documentation when you are interested in the reasons for this. (Defining TLS_ALLOC forces the use of the TlsAlloc() family functions from the Win32 API.)

The complete API is kept very simple:

tls_ptr<A> pA;         // declare an object of class A
pA.reset(new A);       // create a tls of class A when needed
pA.reset(new A(45));   // create a tls of class A with a custom constructor
                       // note, that this also deletes any prior objects
                       // that might have been allocated to pA
pA.release();          // same as pA.reset(0), releases the thread local <BR>                       // object
A& refA = *pA;         // get a temporary reference to the contained object<BR>                       // for faster access
pA->the_answer_is();   // access the object 

Please again note, that it is not necessary to explicitely call the destructors of your class (or release()). This is very handy, when you are writing a piece of code, that has no control over the calling threads, but must still be multithread safe. One caveat however: The destructors of your class are called _after_ the CRT code has ended the thread. Consequently when you are doing something fancy in your destructors, which causes the CRT to reallocate its internal thread local storage pointers, you will be left with a small memory leak of the CRT. This is comparable in effect to the case when you are using the native Win32 API functions to create a thread, instead of _beginthread().

In principle that is all you need. But wait! I mentioned a small bug in the version 6 of the compiler. Luckily it is easy to work around. I provided an include file tlsfix.h which you will need to include into your program. You need to make sure it is getting included before windows.h. To be more precise: the TLS library must be searched before the default CRT library. So you alternatively may specify the library on the command line on the first place, and omit the inclusion of tlsfix.h.

Background

I will not discuss the user interface in this place. It suffices to say, that it essentialy is the same as in the boost library. However I omitted the feature of beeing able to specify arbitrary deleter functions, since this would have raised the need to include the boost library in my code. I wanted to keep it small and just demonstrate the principles. However, my implementation also deviates from boost insofar as I am featuring native compiler support for TLS variables, thus gaining an almost 4 times speed improvement. No need to say, that my implementation of course is Windows specific.

When thinking about TLS for C++ the main question is how to run the constructors and destructors. A careful study of the PE format (e.g. in the MSDN library) reveals, that it almost ever provided for TLS support. (Thanks again to Aaron W. LaFramboise who read it carefully enough.) Of special interest is the section about TLS-Callback:

The program can provide one or more TLS callback functions (though Microsoft 
compilers do not currently use this feature) to support additional 
initialization and termination for TLS data objects. A typical reason to use 
such a callback function would be to call constructors and destructors for 
objects.

Well it is true, that the compilers do not use the feature, but there is nothing that prevents user code to use it though. One somehow must convince the compiler (to be honest it is the linker) to place your callback in a manner, so the operating system will call it. It turns out, that this is surprisingly simple (omitting the deatils for a moment).

// declare your callback
void NTAPI on_tls_callback(PVOID h, DWORD dwReason, PVOID pv)
{
    if( DLL_THREAD_DETACH == dwReason )
        basic_tls::thread_term();
}

// put a pointer in a special segment
#pragma data_seg(".CRT$XLB")
PIMAGE_TLS_CALLBACK p_thread_callback = on_tls_callback;
#pragma data_seg()

You can even add more callbacks, by appending pointers to the ".CRT$XLB" segment. The fancy definitions are available from the windows.h and winnt.h include files in turn.

Now about the details: You will find at times, that your callbacks are not getting called. The reason for this is when the linker does not correctly wire up your segments. It turns out, that this coincides with when you are not using any __declspec(thread) in your code. A further study of the PE format description reveals:

The Microsoft run-time library facilitates this process by defining a memory image of the TLS Directory and giving it the special name “__tls_used” (Intel x86 platforms) or “_tls_used” (other platforms). The linker looks for this memory image and uses the data there to create the TLS Directory. Other compilers that support TLS and work with the Microsoft linker must use this same technique.

Consequentyly, when the linker does not find the _tls_used symbol it won't wire in your callbacks. Luckily this is easy to circumvent:

#pragma comment(linker, "/INCLUDE:__tls_used")

This will pull in the code from CRT that manages TLS. When using a version 7 compiler, that is all you need. (Actually I tried this with 7.1.) It turns out, however that using a version 6 compiler does not work. But the operating system cannot be the culprit, since code compiled by version 7 does work properly. After a little guess-work you will find out, that the CRT code from version 6 is slightly broken, because it inserts a wrong offset to the callback table. It is easy then to replace the errenous code and convince the linker to wire in the work around before the broken version from the CRT. You can study the tlsfix.c file from my submission, if you are interested in the details.

Points of Interest

Which is the first function of your program that is getting called by the operating system? Of course it is not main(). This was easy. Then mainCRTStartup specified as the entry-point in the linker comes to mind. Wrong again. Interestingly the first function beeing called is the Tls-Callback with Reason == DLL_PROCESS_ATTACH. But wait. Don't rely on this. This is not true on WinXP. I observed this on Win2000 only.

I did not yet try the code on Win95/98, WinXP-Home-Edition and Win2003. I would be interested on feedback about using this code on these platforms. In principle it should work, because it is a feature of PE and not the operating system, but ...

History

08.28.2004 Uploaded documentation, source and sample code.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here

About the Author

Roland Schwarz



Austria Austria

Member

posted on 2012-06-27 17:27 Tim 閱讀(666) 評(píng)論(0)  編輯 收藏 引用


只有注冊(cè)用戶登錄后才能發(fā)表評(píng)論。
網(wǎng)站導(dǎo)航: 博客園   IT新聞   BlogJava   博問(wèn)   Chat2DB   管理


<2012年6月>
272829303112
3456789
10111213141516
17181920212223
24252627282930
1234567

導(dǎo)航

統(tǒng)計(jì)

公告

本博客原創(chuàng)文章,歡迎轉(zhuǎn)載和交流。不過(guò)請(qǐng)注明以下信息:
作者:TimWu
郵箱:timfly@yeah.net
來(lái)源:m.shnenglu.com/Tim
感謝您對(duì)我的支持!

留言簿(9)

隨筆分類(173)

IT

Life

搜索

積分與排名

最新隨筆

最新評(píng)論

閱讀排行榜

青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品
  • <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            午夜精品福利一区二区三区av| 欧美高清一区| 亚洲一区二区三区乱码aⅴ蜜桃女| 欧美日韩中文字幕在线视频| 亚洲女同精品视频| 先锋影音久久| 亚洲电影免费在线 | 国产美女诱惑一区二区| 久久riav二区三区| 免费看黄裸体一级大秀欧美| 一区二区三区蜜桃网| 亚洲欧美日韩一区二区| **欧美日韩vr在线| 一区二区三区国产在线| 国产一区二区三区自拍| 亚洲黄色一区二区三区| 国产精品国产a| 欧美ed2k| 国产精品美腿一区在线看 | 久久婷婷国产综合尤物精品| 欧美大片在线看免费观看| 亚洲综合色婷婷| 久久久99久久精品女同性| 一区二区欧美激情| 久久久久九九九| 一区二区三区四区精品| 欧美在线视频免费观看| 国产精品99久久久久久www| 欧美在线资源| 午夜精品久久久久久| 9久草视频在线视频精品| 亚洲欧美视频| 一区二区三区www| 久久人人97超碰精品888| 午夜精品视频| 欧美精品色综合| 男同欧美伦乱| 国产色视频一区| 夜夜爽av福利精品导航| 亚洲国产欧美久久| 久久精品国产99| 欧美一区网站| 国产精品jizz在线观看美国| 亚洲国产老妈| 在线精品视频一区二区三四| 亚洲欧美在线aaa| 亚洲制服欧美中文字幕中文字幕| 裸体歌舞表演一区二区| 久久久久久亚洲精品中文字幕| 欧美午夜电影在线| 亚洲人成绝费网站色www| 亚洲国产精品精华液网站| 欧美在线一二三四区| 欧美在线不卡视频| 国产久一道中文一区| 亚洲一二三区在线观看| 亚洲午夜91| 国产精品国产馆在线真实露脸| 亚洲精品乱码久久久久久黑人 | 久久精品1区| 国产日韩精品电影| 羞羞色国产精品| 久久久久久尹人网香蕉| 国内视频一区| 久久久噜噜噜久久中文字免| 美日韩精品免费观看视频| 狠狠色狠色综合曰曰| 久久久久九九视频| 欧美国产综合一区二区| 亚洲日本va午夜在线影院| 美女主播视频一区| 亚洲精品视频中文字幕| 亚洲视频二区| 国产麻豆午夜三级精品| 久久精品亚洲一区| 欧美成人影音| 亚洲午夜久久久久久尤物| 国产精品乱码一区二区三区| 欧美一区三区二区在线观看| 美女网站在线免费欧美精品| 91久久综合| 国产精品久久二区二区| 久久成人免费| 亚洲国产一区二区a毛片| 一区二区三区日韩精品| 国产日韩欧美综合精品| 久热爱精品视频线路一| 日韩亚洲国产精品| 久久精品人人做人人爽| 亚洲人成网站色ww在线| 国产精品第一区| 久久久久久久高潮| 亚洲伦理在线免费看| 久久经典综合| 一区二区三区欧美亚洲| 国产一区免费视频| 欧美区在线播放| 欧美有码视频| 亚洲免费电影在线观看| 欧美精品免费视频| 欧美一区午夜精品| 亚洲毛片在线观看| 久久综合影音| 亚洲天堂男人| 亚洲欧洲一区二区三区在线观看| 国产精品高潮呻吟视频| 久久综合色一综合色88| 亚洲自拍偷拍福利| 亚洲黄色大片| 美女精品视频一区| 亚洲欧美日韩精品| 亚洲美女免费视频| 激情婷婷亚洲| 国产日产欧产精品推荐色 | 在线播放中文字幕一区| 国产精品嫩草99a| 欧美sm视频| 久久精品99久久香蕉国产色戒| 中国亚洲黄色| 亚洲国产日韩精品| 欧美mv日韩mv国产网站app| 午夜在线视频一区二区区别| 一区二区免费在线观看| 91久久黄色| 悠悠资源网亚洲青| 国产综合久久久久久鬼色| 国产精品美女久久| 欧美午夜宅男影院| 欧美日韩精品系列| 欧美激情在线有限公司| 欧美国产视频在线| 欧美wwwwww| 欧美超级免费视 在线| 久久这里只有精品视频首页| 久久久久久久久久久久久久一区 | 久久久久成人精品| 欧美一区二区三区在线视频| 亚洲欧美日韩中文视频| 亚洲女同在线| 欧美专区第一页| 久久国产精品99国产精| 久久精品人人做人人爽| 久久裸体视频| 美乳少妇欧美精品| 欧美激情导航| 欧美日韩中文字幕精品| 国产精品久久久999| 国产欧美一区二区三区另类精品 | 亚洲成人资源网| 亚洲欧洲日本mm| 一本色道精品久久一区二区三区| 99re6热在线精品视频播放速度| 99国产精品| 亚洲永久精品大片| 久久国产欧美日韩精品| 久久久亚洲欧洲日产国码αv| 免费一级欧美片在线观看| 欧美国产精品日韩| 国产精品国产a| 国产一区二区三区av电影| 亚洲国产高清一区| 中文精品视频| 欧美在线二区| 亚洲大片在线| 中文av一区特黄| 久久精品视频在线看| 欧美麻豆久久久久久中文| 国产精品免费一区二区三区在线观看 | 欧美成人中文字幕| 欧美午夜理伦三级在线观看| 国产日韩av一区二区| 91久久精品一区二区别| 亚洲自拍电影| 欧美国产成人精品| 亚洲午夜精品视频| 免费成人在线观看视频| 国产精品成人v| 亚洲福利一区| 欧美一级黄色录像| 欧美高清你懂得| 亚洲欧美日韩在线不卡| 欧美激情一区在线观看| 国产在线国偷精品产拍免费yy| 亚洲日韩欧美视频| 久久久精品2019中文字幕神马| 亚洲青色在线| 久久尤物视频| 国产偷久久久精品专区| 一本色道精品久久一区二区三区 | 亚洲精品日韩激情在线电影| 久久av二区| 一区二区欧美日韩| 欧美成人伊人久久综合网| 国产亚洲欧美一区二区三区| 亚洲午夜久久久| 亚洲黄色天堂| 美脚丝袜一区二区三区在线观看| 国产欧美日韩亚洲精品| 在线一区二区三区做爰视频网站 | 亚洲女女做受ⅹxx高潮|