From: Paulo Marques <pmarques@grupopie.com>
To: "Chad N. Tindel" <chad@tindel.net>
Cc: Chris Friesen <cfriesen@nortel.com>,
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 19:04:08 +0000 [thread overview]
Message-ID: <421E2528.8060305@grupopie.com> (raw)
In-Reply-To: <20050224183851.GA24359@calma.pair.com>
Chad N. Tindel wrote:
>>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.
>
>
> Come now. There is no such thing as a random kernel thread. Any General
> Purpose kernel needs the ability to do work that keeps the entire system from
> grinding to a halt.
FYI most kernel threads do background work, that doesn't have hard
real-time constraints. Why should my audio recording session get
interrupted (read: "sent to the trashcan") just because the swap daemon
decided that it was a good time to write some pages out? Couldn't it
have waited just a few more milliseconds?
You don't seem to realize that you have just arrived to this mailing
list and missed years of discussions on kernel architecture.
If you keep a learning attitude, there is a chance for this discussion
to go on. However, if you keep the "Come now, don't bullshit me, this is
a broken architecture and you're just trying to cover up" attitude,
you're just going to get discarded as a troll.
I personally like the linux way: "root has the ability to shoot himself
in the foot if he wants to". This is my computer, damn it, I am the one
who tells it what to do.
This is much, much better than the "users are stupid, we must protect
them from themselves" kind of way that other OS'es use.
Just my 0.02 euros,
--
Paulo Marques - www.grupopie.com
All that is necessary for the triumph of evil is that good men do nothing.
Edmund Burke (1729 - 1797)
next prev parent reply other threads:[~2005-02-24 19:04 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
2005-02-24 18:38 ` Chad N. Tindel
2005-02-24 19:04 ` Paulo Marques [this message]
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=421E2528.8060305@grupopie.com \
--to=pmarques@grupopie.com \
--cc=EFAULT@gmx.de \
--cc=akpm@osdl.org \
--cc=cfriesen@nortel.com \
--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.