All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: xenoka09@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] More blackfin kernel oops under heavy load
Date: Mon, 28 Feb 2011 14:52:25 +0100	[thread overview]
Message-ID: <4D6BA899.90600@domain.hid> (raw)
In-Reply-To: <alpine.DEB.1.10.1102281353490.12109@domain.hid>

Kolja Waschk wrote:
>>> Yes. I just tried and replaced the select with a loop accept()ing on the now
>>> nonblocking socket plus some usleep() and still the fault occurs as with
>>> select(). No other thread in the current setup uses select().
>> Mmmm busy waiting? But is Linux able to run from time to time?
> 
> Yes, an usleep(100000) after each "check" of all sockets allowed me to telnet
> into the system while the server runs, for example

I do not really understand what we are talking about. Are we talking
about Linux select/accept or Xenomai select/accept? Why not using the
blocking accept?

-- 
					    Gilles.


  reply	other threads:[~2011-02-28 13:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 11:44 [Xenomai-help] More blackfin kernel oops under heavy load Kolja Waschk
2011-02-28 12:08 ` Gilles Chanteperdrix
2011-02-28 12:25   ` Kolja Waschk
2011-02-28 12:19     ` Gilles Chanteperdrix
2011-02-28 12:48       ` Kolja Waschk
2011-02-28 12:41         ` Gilles Chanteperdrix
2011-02-28 12:56           ` Kolja Waschk
2011-02-28 13:52             ` Gilles Chanteperdrix [this message]
2011-02-28 18:46               ` Kolja Waschk
2011-03-01 10:50                 ` Kolja Waschk
2011-03-06  4:17                   ` Philippe Gerum
2011-03-06 11:58                     ` Kolja Waschk
2011-03-01 12:13                 ` Gilles Chanteperdrix
2011-03-01 17:47                   ` 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=4D6BA899.90600@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=xenoka09@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.