All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] __thread instead of pthread_get/setspecific
Date: Mon, 13 Oct 2008 23:55:48 +0200	[thread overview]
Message-ID: <48F3C3E4.4020801@domain.hid> (raw)

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

Hi,

looking into the "xeno_in_primary_mode" thing I wondered how to make the
thread state quickly retrievable. Going via pthread_getspecific as we do
for xeno_get_current appears logical - but not optimal. Though
getspecific is optimized for speed, it remains a function call, a few
sanity checks, and only finally a TLS variable access. That could be
achieved in a much lighter way by using a __thread variable.

But can we assume that all target we support also support the __thread
storage class? TLS is surely mandatory now: I assume pthread_getspecific
would become non-RT safe without it, right? Is there anything we
can/must check for during configure to verify __thread support?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

             reply	other threads:[~2008-10-13 21:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 21:55 Jan Kiszka [this message]
2008-10-14  8:28 ` [Xenomai-core] __thread instead of pthread_get/setspecific 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
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=48F3C3E4.4020801@domain.hid \
    --to=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.