From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Fast userspace locks for native skin
Date: Fri, 22 Aug 2008 12:33:46 +0200 [thread overview]
Message-ID: <48AE960A.9070501@domain.hid> (raw)
In-Reply-To: <48AE852D.3020506@domain.hid>
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Gilles Chanteperdrix wrote:
>>> decision (we could store the first pending thread priority in a
>>> user/kernel shared area, with the complication that we would need
>>> updating this priority if it ever changes, but to get the priority of
>>> the current thread, we also need a syscall, moreover switching to
>>> secondary mode).
>> I'm not thinking about the case where there is already someone waiting.
>> That will need a kernel entry anyway (the low-prio waiter may sit on
>> some other CPU...). But in case signaling always happens before pending,
>> there is no need at all to consult the kernel.
>
> In this case, you can avoid calling pthread_cond_signal at all... So, if
> you are stupid enough to call pthread_cond_signal when no-one is
> waiting, you deserve a syscall anyway.
Yes, algorithmically avoidable. OK, let's see if there is someone who
actually has a need for it (legacy code...).
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2008-08-22 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 19:25 [Xenomai-core] Fast userspace locks for native skin Jan Kiszka
2008-08-21 19:29 ` Gilles Chanteperdrix
2008-08-21 19:36 ` Gilles Chanteperdrix
[not found] ` <48ADC493.7000009@domain.hid>
2008-08-21 19:53 ` Gilles Chanteperdrix
2008-08-22 9:18 ` Jan Kiszka
2008-08-22 9:21 ` Gilles Chanteperdrix
2008-08-22 10:33 ` Jan Kiszka [this message]
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=48AE960A.9070501@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.