All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] __thread instead of pthread_get/setspecific
Date: Tue, 14 Oct 2008 12:25:38 +0200	[thread overview]
Message-ID: <48F473A2.1050104@domain.hid> (raw)
In-Reply-To: <48F46954.6050704@domain.hid>

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), there
is no point in sticking with pthread_getspecific. At least on x86 the
advantage is easily visible (==no more function calls). That's also due
to the lighter concept of __thread: it pushes the key resolution from
runtime to compile/link-time.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2008-10-14 10:25 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 [this message]
2008-10-14 12:18             ` Gilles Chanteperdrix
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=48F473A2.1050104@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.