All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Daniel Schnell <daniel.schnell@domain.hid>
Cc: xenomai@xenomai.org
Subject: RE: [Xenomai-help] Kernel-OOps
Date: Tue, 27 Feb 2007 20:03:23 +0100	[thread overview]
Message-ID: <1172603004.10171.24.camel@domain.hid> (raw)
In-Reply-To: <DD39B5C3F4963040ADC9768BE7E430CB01B53705@domain.hid>

On Tue, 2007-02-27 at 14:51 +0000, Daniel Schnell wrote:
> Philippe Gerum wrote:
> >
> > Some usage patterns involving permanent mode switches inside a large
> > set of real-time threads that only rarely relinquish the CPU to other
> > regular Linux tasks may cause this. This is specific to 2.4 kernels.
> > I will raise this value in the next patch update. Thanks,   
> 
> I think simply increasing this value to some other magic number could
> not be enough until somebody stumbles again upon this limit. How about
> implementing a kernel configuration option with a default value
> (although it is only 2.4 specific) ? This is probably a ipipe patch
> specific option ?
> 

It's not a magic value, it means that up to 32 memory contexts may be
stalled in the drop queue at any point in time, waiting for a normal
Linux task to be switched in to flush them, while a large number of
Xenomai threads is going through frequent domain migrations. Hitting
this limit _is_ where the problem lies, not the static limit itself, and
it tells that something needs to be fixed in the application, so that it
does not starve the regular Linux activities this way.

IOW, it's ok to raise this compile-time value to account for
applications living on the edge, but we should not make a feature out of
an application design issue, by adding such a configuration knob.

-- 
Philippe.




  reply	other threads:[~2007-02-27 19:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 13:25 [Xenomai-help] Kernel-OOps Daniel Schnell
2007-02-27 13:53 ` Daniel Schnell
2007-02-27 14:38   ` Philippe Gerum
2007-02-27 14:51     ` Daniel Schnell
2007-02-27 19:03       ` Philippe Gerum [this message]
2007-02-28  8:59         ` Daniel Schnell
2007-02-28 10:35           ` Philippe Gerum
2007-02-28 14:25             ` Daniel Schnell

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=1172603004.10171.24.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=daniel.schnell@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.