From: yodaiken@fsmlabs.com
To: george anzinger <george@mvista.com>
Cc: Tyson D Sawyer <tyson@rwii.com>, linux-kernel@vger.kernel.org
Subject: Re: Missed jiffies
Date: Sat, 16 Feb 2002 09:14:05 -0700 [thread overview]
Message-ID: <20020216091405.D29832@hq.fsmlabs.com> (raw)
In-Reply-To: <3C6E77DE.70FE49DF@rwii.com> <3C6E833F.1A888B3C@mvista.com>
In-Reply-To: <3C6E833F.1A888B3C@mvista.com>; from george@mvista.com on Sat, Feb 16, 2002 at 08:05:19AM -0800
On Sat, Feb 16, 2002 at 08:05:19AM -0800, george anzinger wrote:
> I think the real problem needs to be addressed, i.e. why does the SMI
> (and/ or other code) keep the interrupt system off so long. Most
> interrupts are completed in micro seconds, not milliseconds, lets fix
> the real problem.
The SMI is an unbearable abomination and it is an issue that even Microsoft
has been unable to make Intel respond to properly. It makes Rambus seem brilliant.
The basic idea: take a high speed well optimized processor that is the most
critical performance component of your system and arbitrarily divert it to managing
fans completely outside of OS control is so unbearably stupid, arrogant, ugly and
nauseating as to be hard to believe even in this industry.
--
---------------------------------------------------------
Victor Yodaiken
Finite State Machine Labs: The RTLinux Company.
www.fsmlabs.com www.rtlinux.com
next prev parent reply other threads:[~2002-02-16 16:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-16 15:16 Missed jiffies Tyson D Sawyer
2002-02-16 16:05 ` george anzinger
2002-02-16 16:14 ` yodaiken [this message]
2002-02-16 17:11 ` Alan Cox
2002-02-17 2:18 ` disregard lee johnson
2002-02-17 22:48 ` Missed jiffies H. Peter Anvin
2002-02-18 19:04 ` george anzinger
2002-02-18 19:22 ` H. Peter Anvin
2002-02-18 19:33 ` Alan Cox
[not found] ` <a4pbvi@cesium.transmeta.com>
2002-02-19 9:30 ` Pavel Machek
2002-02-19 20:23 ` H. Peter Anvin
2002-02-16 16:46 ` Alan Cox
2002-02-16 18:44 ` Eric W. Biederman
2002-02-16 19:02 ` george anzinger
2002-02-19 9:25 ` Pavel Machek
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=20020216091405.D29832@hq.fsmlabs.com \
--to=yodaiken@fsmlabs.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tyson@rwii.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox