From: "Chad N. Tindel" <chad@tindel.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Xterm Hangs - Possible scheduler defect?
Date: Thu, 24 Feb 2005 00:26:30 -0500 [thread overview]
Message-ID: <20050224052630.GA99960@calma.pair.com> (raw)
In-Reply-To: <20050223183634.31869fa6.akpm@osdl.org>
> But the other side of the coin is that a SCHED_FIFO userspace task
> presumably has extreme latency requirements, so it doesn't *want* to be
> preempted by some routine kernel operation. People would get irritated if
> we were to do that.
Just to follow up a bit. People writing apps that run at SCHED_FIFO know
that they aren't getting hard real-time, and they are OK with that. If they
wanted something more they'd run on RTLinux. Why would it be wrong to preempt
the SCHED_FIFO process in the case, assuming that it is too hard to fix a broken
design that doesn't allow the necessary kernel threads to run on any CPU?
Chad
next prev parent reply other threads:[~2005-02-24 5:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 23:06 Xterm Hangs - Possible scheduler defect? Chad N. Tindel
2005-02-24 2:36 ` Andrew Morton
2005-02-24 5:23 ` Chad N. Tindel
2005-02-24 6:50 ` Andrew Morton
2005-02-24 5:26 ` Chad N. Tindel [this message]
2005-02-24 13:25 ` Helge Hafting
2005-02-24 17:33 ` Chad N. Tindel
2005-02-24 22:25 ` Peter Chubb
2005-02-24 22:40 ` Chad N. Tindel
2005-02-24 23:00 ` Andrew Morton
2005-02-24 23:22 ` Chris Friesen
2005-02-24 23:32 ` Andrew Morton
2005-02-25 0:47 ` Kyle Moffett
[not found] <20050224075756.GA18639@calma.pair.com>
[not found] ` <30111.1109237503@www1.gmx.net>
2005-02-24 17:53 ` Chad N. Tindel
2005-02-24 18:19 ` Chris Friesen
2005-02-24 18:38 ` Chad N. Tindel
2005-02-24 19:04 ` Paulo Marques
2005-02-24 19:22 ` Chad N. Tindel
2005-02-24 19:46 ` Chris Friesen
2005-02-24 20:08 ` Chad N. Tindel
2005-02-24 20:29 ` Chris Friesen
2005-02-25 0:51 ` Ingo Oeser
2005-02-25 15:12 ` Chris Friesen
2005-02-25 15:39 ` Ingo Oeser
2005-02-25 15:53 ` Paulo Marques
2005-02-25 16:24 ` Lee Revell
2005-02-25 17:07 ` Chris Friesen
2005-02-24 19:52 ` Barry K. Nathan
2005-02-25 20:25 ` Helge Hafting
2005-02-25 21:02 ` Chad N. Tindel
2005-02-25 23:24 ` Lee Revell
2005-02-26 11:58 ` Helge Hafting
2005-02-25 4:25 ` Mike Galbraith
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=20050224052630.GA99960@calma.pair.com \
--to=chad@tindel.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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.