From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] __thread instead of pthread_get/setspecific
Date: Tue, 14 Oct 2008 14:18:54 +0200 [thread overview]
Message-ID: <48F48E2E.2050004@domain.hid> (raw)
In-Reply-To: <48F473A2.1050104@domain.hid>
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> Jan Kiszka wrote:
>>> It will always remain orders of magnitude heavier than __thread
>>> variables which are a) inlined and b) should only need two memory
>>> accesses at worst. Moreover, it is clearly the future, while the
>>> importance of pthread_getspecific will decrease over the time. The
>>> __thread storage class is C99 standard (though its implementation
>>> remains a separate topic).
>> You are exagerating a bit: pthread_getspecific is pretty efficient
>> already (from the few things that I have timed on ARM, it is the only
>> one which takes under the microsecond). That you will gain something
>> with __thread is not guaranteed by the C99 standard either: in fact the
>> implementation could use exactly the same functions.
>
> As long as we do not loose anything (performance or portability),
You loose portability. But I agree that we do not care much.
--
Gilles.
next prev parent reply other threads:[~2008-10-14 12:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 21:55 [Xenomai-core] __thread instead of pthread_get/setspecific Jan Kiszka
2008-10-14 8:28 ` Gilles Chanteperdrix
2008-10-14 9:08 ` Jan Kiszka
2008-10-14 9:15 ` Gilles Chanteperdrix
2008-10-14 9:26 ` Jan Kiszka
2008-10-14 9:41 ` Gilles Chanteperdrix
2008-10-14 10:25 ` Jan Kiszka
2008-10-14 12:18 ` Gilles Chanteperdrix [this message]
2008-10-14 12:49 ` Jan Kiszka
2008-10-14 12:53 ` Gilles Chanteperdrix
2008-10-14 12:59 ` Jan Kiszka
2008-10-14 13:02 ` Gilles Chanteperdrix
2008-10-14 13:09 ` Jan Kiszka
2008-10-14 13:22 ` Gilles Chanteperdrix
2008-10-14 13:25 ` Gilles Chanteperdrix
2008-10-14 13:44 ` Jan Kiszka
2008-10-14 14:30 ` Philippe Gerum
2008-10-14 9:58 ` Gilles Chanteperdrix
2008-10-14 10:26 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48F48E2E.2050004@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.