From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
Ronny Meeus <ronny.meeus@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] [xenomai-forge] timer-internal consume a lot of cpu
Date: Thu, 18 Dec 2014 15:58:52 +0100 [thread overview]
Message-ID: <5492EBAC.10502@siemens.com> (raw)
In-Reply-To: <20141218141248.GN2012@hermes.click-hack.org>
On 2014-12-18 15:12, Gilles Chanteperdrix wrote:
> On Thu, Dec 18, 2014 at 01:28:42PM +0100, Ronny Meeus wrote:
>> On Thu, Dec 18, 2014 at 10:04 AM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>>> On 2014-12-18 09:00, Ronny Meeus wrote:
>>>>>
>>>>> A release of the glibc that fixes this issue. I must admit that I did
>>>>> not track this problem lately. Jan likely knows better here.
>>>>>
>>>>
>>>> Jan,
>>>>
>>>> what version glibc solves the priority inversion issue on conditional variables?
>>>> I already tried the glibc 2.18 but the issue is still there.
>>>
>>> The bug is still not fixed, and discussion stalled again, see
>>> https://sourceware.org/bugzilla/show_bug.cgi?id=11588
>>>
>>> Jan
>>>
>>> --
>>> Siemens AG, Corporate Technology, CT RTC ITP SES-DE
>>> Corporate Competence Center Embedded Linux
>>
>> Philippe, Jan
>>
>> as long as this issue is not fixed in glibc, it is not OK to use
>> conditional variables
>
> I believe xenomai cobalt does not suffer from the same issue,
> condition variables should work fine with priority inheritance.
Yes, this is a mercury-only issue. Cobalt is fine as its own
implementation of posix mutexes and condvars is correct in this regard.
>
> Otherwise, have you tried some alternate libc, such as musl:
> http://www.musl-libc.org/
>
> The following blog:
> http://ewontfix.com/
>
> Seems to show that the musl maintainers try and report glibc bugs
> and avoid them in their implementation.
>
> I have not tried xenomai with musl at all, so, maybe it does not
> even compile. But maybe just compiling a testcase for the condvar
> issue with that libc would help know if it has the same issue or
> not.
Well, like with many of those "light-weight" re-implementations, the are
"small" issues with bits required for real-time:
http://git.musl-libc.org/cgit/musl/tree/src/thread/pthread_mutexattr_setprotocol.c
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-12-18 14:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 16:26 [Xenomai] [xenomai-forge] timer-internal consume a lot of cpu Ronny Meeus
2014-12-16 17:36 ` Ronny Meeus
2014-12-16 17:58 ` Philippe Gerum
2014-12-16 19:41 ` Ronny Meeus
2014-12-16 20:07 ` Philippe Gerum
2014-12-18 8:00 ` Ronny Meeus
2014-12-18 9:04 ` Jan Kiszka
2014-12-18 12:28 ` Ronny Meeus
2014-12-18 13:35 ` Jan Kiszka
2014-12-18 14:17 ` Ronny Meeus
2014-12-18 14:12 ` Gilles Chanteperdrix
2014-12-18 14:58 ` Jan Kiszka [this message]
2014-12-18 15:04 ` Gilles Chanteperdrix
2014-12-18 15:25 ` Ronny Meeus
2014-12-18 15:30 ` Gilles Chanteperdrix
2014-12-18 15:35 ` Jan Kiszka
2014-12-18 15:49 ` Ronny Meeus
2014-12-18 16:06 ` Jan Kiszka
2014-12-18 17:21 ` Ronny Meeus
2014-12-23 17:36 ` Ronny Meeus
2015-01-23 16:45 ` Philippe Gerum
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=5492EBAC.10502@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=ronny.meeus@gmail.com \
--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.