All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Ronny Meeus <ronny.meeus@gmail.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, xenomai@xenomai.org
Subject: Re: [Xenomai] [xenomai-forge] timer-internal consume a lot of cpu
Date: Thu, 18 Dec 2014 16:30:01 +0100	[thread overview]
Message-ID: <20141218153001.GT2012@hermes.click-hack.org> (raw)
In-Reply-To: <CAMJ=MEc2V0P4nLXVwmxn7LNuY92PrPg=TnPa6UJi=0oCRz=w0g@mail.gmail.com>

On Thu, Dec 18, 2014 at 04:25:40PM +0100, Ronny Meeus wrote:
> On Thu, Dec 18, 2014 at 4:04 PM, Gilles Chanteperdrix
> <gilles.chanteperdrix@xenomai.org> wrote:
> > On Thu, Dec 18, 2014 at 03:58:52PM +0100, Jan Kiszka wrote:
> >> On 2014-12-18 15:12, Gilles Chanteperdrix wrote:
> >> > 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
> >
> > On the other hand, no implementation with a clear ENOTSUPP is better
> > than a partial and buggy implementation that can not be trusted anyway.
> >
> > --
> >                                             Gilles.
> 
> Gilles I agree.
> 
> In the meantime I tried it already.
> 
> This is indeed the trace I get when running my test application with musl.
> # ./cond_test_arm
> # hread_mutexattr_setprotocol: Not supported
> 
> Cobalt is not an option for us either since in that case all Linux
> applications will run in low-priority. Next to that we also have a
> huge priority inversion each time a Linux system call is done.
> 
> Do we have other options to fix forge?

Well, three options have been proposed if I followed this thread
correctly: 
- stop using priority inheritance for these internal mutexes, at the
risk of creating priority inversions
- switch to priority ceiling (but what will be the ceiling? 99?)
- use cobalt.

-- 
					    Gilles.


  reply	other threads:[~2014-12-18 15:30 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
2014-12-18 15:04                   ` Gilles Chanteperdrix
2014-12-18 15:25                     ` Ronny Meeus
2014-12-18 15:30                       ` Gilles Chanteperdrix [this message]
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=20141218153001.GT2012@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@siemens.com \
    --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.