From: Chris Friesen <cfriesen@nortel.com>
To: "Chad N. Tindel" <chad@tindel.net>
Cc: Mike Galbraith <EFAULT@gmx.de>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Xterm Hangs - Possible scheduler defect?
Date: Thu, 24 Feb 2005 12:19:45 -0600 [thread overview]
Message-ID: <421E1AC1.1020901@nortel.com> (raw)
In-Reply-To: <20050224175331.GA18723@calma.pair.com>
Chad N. Tindel wrote:
> 1. Kernel preempts all. There may be some hierarchy of kernel priorities
> too, but it isn't important here.
> 2. SCHED_FIFO processes preempt all userspace applications.
> 3. SCHED_RR.
> 4. SCHED_OTHER.
>
> Under no circumstances should any single CPU-bound userspace thread completely
> hose a 64-way SMP box.
>
> Can somebody educate me on why it is correct to do it any other way?
Low-latency userspace apps. The audio guys, for instance, are trying to
get latencies down to the 100us range.
If random kernel threads can preempt userspace at any time, they wreak
havoc with latency as seen by userspace.
Chris
next prev parent reply other threads:[~2005-02-24 18:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050224075756.GA18639@calma.pair.com>
[not found] ` <30111.1109237503@www1.gmx.net>
2005-02-24 17:53 ` Xterm Hangs - Possible scheduler defect? Chad N. Tindel
2005-02-24 18:19 ` Chris Friesen [this message]
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
2005-02-23 23:06 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
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
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=421E1AC1.1020901@nortel.com \
--to=cfriesen@nortel.com \
--cc=EFAULT@gmx.de \
--cc=akpm@osdl.org \
--cc=chad@tindel.net \
--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.