The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] OT: critical Intel design flaw
Date: Wed, 3 Jan 2018 09:26:40 -0500	[thread overview]
Message-ID: <CAC20D2NEvx_3R_HjzO6r3h6OaAcrpkmWuTRNX7-ApoEz8+KxTg@mail.gmail.com> (raw)
In-Reply-To: <20180103134358.3F16818C098@mercury.lcs.mit.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]

below..

On Wed, Jan 3, 2018 at 8:43 AM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:

>
> I'm highly amused by the irony. Intel throws bazillions of transistors at
> these hyper-complex CPUs in an attempt to make them as fast as possible -
> and
> (probably because of the complexity) missed a bug, the fix for which
> involves... slowing things way down!
>

​+1 however... I think there is a corollary ​

>
> I wonder how many other bugs are lurking in these hyper-complex designs?
> Didn't anyone at Intel stop to think that complexity is bad, in and of
> itself?
>
​Exactly....​
​ and a loud "Amen Brother Chiappa​
."
​

IIRC this is part of the argument Dykstra made with the THE paper years
ago, Parnas in his information hiding paper -- i.e. why microkernels and
proper layering are a good idea.   Keep is simple and do one thing
well/protect yourself against other subsystems not being 100%.  Linux and
Winders are are bad a the processor.

​Yup microkernels are a tad slower and have more overhead, and might
(probably will) cost a little more.   But I really do think simplicity
beats complexity and I'll pay a bit in over head to keep it simple.

The problem of course for my employers over the years, is that many  people
(most
​people ​
probably)
​ ​
do not think me
​ and follow their wallet on the fastest for the cheapest​
;-)

Clem​

ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180103/8daee0d8/attachment.html>


  reply	other threads:[~2018-01-03 14:26 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 13:43 Noel Chiappa
2018-01-03 14:26 ` Clem Cole [this message]
2018-01-03 17:28   ` Bakul Shah
2018-01-03 17:46     ` ron minnich
2018-01-03 18:28       ` Bakul Shah
2018-01-03 18:27     ` Clem Cole
2018-01-03 18:39       ` Forrest, Jon
2018-01-03 18:50         ` ron minnich
2018-01-03 19:56       ` Paul Winalski
2018-01-03 20:24       ` Bakul Shah
2018-01-03 23:40       ` Theodore Ts'o
2018-01-04  0:51         ` Larry McVoy
2018-01-04  2:13           ` Bakul Shah
2018-01-04  2:26             ` Larry McVoy
2018-01-04  3:31               ` Bakul Shah
2018-01-04  2:09         ` Arthur Krewat
2018-01-04  3:21           ` Dan Cross
2018-01-04 17:42             ` Arthur Krewat
2018-01-04 11:53         ` Harald Arnesen
2018-01-04 14:03           ` Clem Cole
2018-01-04 15:54             ` Larry McVoy
2018-01-04 16:45             ` Theodore Ts'o
2018-01-04 17:10               ` Andy Kosela
2018-01-04 17:17               ` Larry McVoy
2018-01-04 18:29                 ` Bakul Shah
2018-01-04 18:50                   ` Larry McVoy
2018-01-04 20:52                     ` Warner Losh
2018-01-04 20:56                       ` Bakul Shah
2018-01-04 20:56                   ` Theodore Ts'o
2018-01-04 21:16                     ` Warner Losh
2018-01-04 22:55                       ` Andy Kosela
2018-01-05 14:27                         ` Clem Cole
2018-01-04 21:17                     ` Bakul Shah
2018-01-04 17:20               ` Tom Ivar Helbekkmo
2018-01-04 17:28                 ` Warner Losh
2018-01-03 17:07 ` Bakul Shah
  -- strict thread matches above, loose matches on Subject: below --
2018-01-03 17:06 Norman Wilson
2018-01-03  7:53 Andy Kosela
2018-01-03 11:57 ` Ron Natalie
2018-01-03 14:22   ` Random832

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=CAC20D2NEvx_3R_HjzO6r3h6OaAcrpkmWuTRNX7-ApoEz8+KxTg@mail.gmail.com \
    --to=clemc@ccc.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;
as well as URLs for NNTP newsgroup(s).