This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: [ECOS] Thread-specific data
- To: guinan@bluebutton.com
- Subject: Re: [ECOS] Thread-specific data
- From: jlarmour@cygnus.co.uk (Jonathan Larmour)
- Date: Sun, 20 Jun 1999 16:34:40 +0100
- Cc: ecos-discuss@sourceware.cygnus.com
- Newsgroups: cygnus.sourceware.ecos.d
- Organization: Cygnus Solutions Ltd, UK
In article <Pine.LNX.3.96.990618144410.26479B-100000@newt.home.net> you write:
>
>In other words, is it true that the cyg_ucount32 returned
>by cyg_thread_new_data_index() is _not_ a per-thread datum
>itself? I would hope not, but I just wanted to clarify the
>issue.
Yes, it (quite sensibly) is not a per-thread value itself :-).
The map of free thread data indexes can be found in the Cyg_Thread class
in kernel/v1_2_1/include/thread.hxx as:
// Map of free thread_data indexes. Each bit represents an index
// and is 1 if that index is free, and 0 if it is in use.
static cyg_ucount32 thread_data_map;
The "static" stops it from being thread-specific.
HTH,
Jifl
--
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK. Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
my brains kept falling out." || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/ These opinions are all my own fault