All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Frederik Bayart <frederik.bayart@triphase.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] cpu usage
Date: Fri, 27 Jul 2012 15:35:03 +0200	[thread overview]
Message-ID: <50129907.5040306@siemens.com> (raw)
In-Reply-To: <CALH4WdYdUKfMrsJUHqQYTh84GgMWErpCYUJMmZVtxxngdNoStQ@mail.gmail.com>

On 2012-07-27 15:04, Frederik Bayart wrote:
> I'm running Xenomai 2.6.0 on Linux 2.6.38
> 
> I have a dual core processor.
> When I run a busywait loop on cpu 0 (see source in attachment), I
> can't do anything anymore on the computer although cpu 1 is almost
> entirely idle. I can't interrupt the busywait loop, login, type
> something in a shell, ...
> This is even the case if I run linux entirely on cpu 1 (by using
> isolcpus=0 as kernel parameter)
> 
> How can this be explained ?
> 
> Is it possible to use cpu 0 at 100% for a xenomai tasks and cpu 1 for
> normal linux tasks so that you can still work on the computer ?

It's a FAQ: This is not possible with current Linux. It will lock up
quite quickly if kernel helper threads for RCU or work queues cannot run
once in a while. Also, time keeping will be affected. Due to the latter,
you should release the core to Linux once every scheduling tick.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux




  parent reply	other threads:[~2012-07-27 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 13:04 [Xenomai] cpu usage Frederik Bayart
2012-07-27 13:21 ` Gilles Chanteperdrix
2012-07-27 13:35 ` Jan Kiszka [this message]
2012-07-27 13:58   ` Frederik Bayart
2012-07-27 14:01     ` Gilles Chanteperdrix
2012-07-27 14:05       ` Gilles Chanteperdrix
2012-07-27 14:42         ` Gilles Chanteperdrix

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=50129907.5040306@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=frederik.bayart@triphase.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.