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

無(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)源:www.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>
            亚洲日本乱码在线观看| 久久精品123| 正在播放亚洲| 国产在线一区二区三区四区 | 亚洲激情女人| 欧美区日韩区| 欧美一区二粉嫩精品国产一线天| 久久精品国产精品亚洲| 亚洲最黄网站| 久久夜色精品国产| 久久精品国产欧美激情| 国产精品久久久久久久一区探花 | 欧美另类高清视频在线| 久久精品一区二区三区不卡| 欧美性大战久久久久| 亚洲国产人成综合网站| 国产一区二区三区久久| 亚洲欧美国产77777| 亚洲欧美国产日韩天堂区| 久久综合伊人77777| 欧美激情一区二区三区全黄| 亚洲国产另类久久精品| 亚洲激情专区| 免费不卡视频| 日韩视频在线观看免费| 亚洲天堂激情| 国产精品国码视频| 午夜亚洲性色福利视频| 久久成人精品| 亚洲大片精品永久免费| 欧美成人精品1314www| 91久久线看在观草草青青| 在线视频免费在线观看一区二区| 欧美精品日韩www.p站| 亚洲美女精品成人在线视频| 亚洲午夜视频在线观看| 国产午夜亚洲精品不卡| 免费日韩av| 亚洲伊人第一页| 亚洲福利电影| 久久久亚洲高清| 亚洲视频在线播放| 韩国三级电影久久久久久| 国产精品ⅴa在线观看h| 毛片精品免费在线观看| 亚洲男人的天堂在线观看 | 美日韩精品免费| 日韩天堂在线视频| 免费在线播放第一区高清av| 亚洲一区免费| 亚洲区第一页| 亚洲人成在线免费观看| 国产美女精品人人做人人爽| 欧美日本三区| 欧美日韩久久久久久| 欧美成人午夜激情视频| 久久久国产91| 欧美在线视频免费| 久久精品国产久精国产思思| 亚洲视频综合| 一区二区久久久久| 在线一区二区三区做爰视频网站 | 欧美伊人久久| 久久激情综合| 性欧美精品高清| 久久综合色88| 亚洲国产欧美日韩| 亚洲国产欧美一区二区三区同亚洲| 欧美激情国产精品| 亚洲视频www| 久久久夜夜夜| 欧美日韩精品欧美日韩精品一 | 1024精品一区二区三区| 亚洲国产欧美日韩另类综合| 亚洲午夜性刺激影院| 欧美在线免费视频| 亚洲高清自拍| 亚洲欧美日韩综合| 免费观看在线综合| 欧美日一区二区三区在线观看国产免 | 女人香蕉久久**毛片精品| 亚洲大胆女人| 亚洲一区国产| 欧美成人激情视频免费观看| 国产精品综合久久久| 99pao成人国产永久免费视频| 午夜在线视频一区二区区别| 欧美丰满少妇xxxbbb| 欧美一区二区三区免费大片| 欧美日韩一区二区三区在线视频| 在线观看日韩av先锋影音电影院| 一本一本大道香蕉久在线精品| 美女尤物久久精品| 欧美专区第一页| 国产手机视频一区二区| 午夜激情一区| 欧美一区=区| 一区二区三区在线观看国产| 亚洲欧美一区二区视频| 99精品福利视频| 国产精品久久久久影院色老大| 亚洲在线第一页| 日韩亚洲欧美成人一区| 欧美精品综合| 亚洲一区二区三区在线看| 亚洲蜜桃精久久久久久久| 欧美激情一二三区| 亚洲一区二区在线| 欧美专区在线观看| 亚洲精品乱码| 亚洲一区二区免费视频| 国产日韩精品一区二区三区在线| 久久久激情视频| 免费在线观看日韩欧美| 亚洲一区免费看| 久久夜色精品国产亚洲aⅴ| 亚洲国产精品久久久久婷婷老年| 麻豆久久婷婷| 国产精品人人做人人爽| 欧美chengren| 国产精品人成在线观看免费| 久久综合网络一区二区| 欧美日韩在线播| 免费视频久久| 国产日本欧美一区二区三区| 亚洲激情成人在线| 亚洲国产精品久久久久秋霞影院 | 国产伦精品一区二区三区| 欧美成人一区二区三区片免费| 欧美精品福利视频| 久久精品99无色码中文字幕| 欧美精品免费视频| 欧美大片免费看| 黄页网站一区| 亚洲欧美大片| 性色av一区二区三区红粉影视| 欧美经典一区二区| 亚洲美女91| 一区二区三区精品视频| 久久资源在线| 美国十次了思思久久精品导航| 国产日韩精品综合网站| 午夜亚洲性色福利视频| 久久精品观看| 国内精品99| 牛牛国产精品| 日韩午夜电影av| 午夜精品久久久久久久99水蜜桃| 欧美午夜一区二区三区免费大片| 亚洲日本成人| 欧美伊人久久久久久久久影院| 国产精品自拍视频| 久久琪琪电影院| 亚洲久久成人| 久久精品色图| 一本色道88久久加勒比精品| 国产精品国产三级欧美二区| 午夜精品视频一区| 久久亚洲国产精品一区二区 | 欧美一区视频| 欧美丰满少妇xxxbbb| 亚洲永久在线| 亚洲茄子视频| 一区二区视频欧美| 欧美激情一二区| 久久久久久夜| 亚洲欧美一区二区原创| 亚洲日本一区二区| 久久一区二区精品| 欧美在线视频导航| 亚洲一区二区三区在线视频| 亚洲福利视频在线| 国产一区二区三区四区三区四| 欧美午夜激情视频| 欧美11—12娇小xxxx| 久久免费国产| 久久精品动漫| 欧美在线二区| 亚洲天堂av在线免费| 亚洲一区二区三区激情| 亚洲理论电影网| 一区二区三区日韩精品视频| 日韩视频精品在线| 亚洲视频网站在线观看| 日韩视频免费大全中文字幕| 欧美激情综合| 亚洲黄色av一区| 亚洲美女性视频| 亚洲欧美中文另类| 久久国产天堂福利天堂| 老司机67194精品线观看| 欧美国产一区二区三区激情无套| 欧美日韩国产一区二区三区地区 | 国产精品久久久久久久久久免费看 | 一区二区三区久久久| 亚洲视频一二三| 欧美v亚洲v综合ⅴ国产v| 欧美国产日韩精品免费观看| 国产精品爱啪在线线免费观看| 国产精一区二区三区|