From: rochkind@basepath.com (Marc Rochkind)
Subject: [TUHS] sort of unrelated but
Date: Mon, 21 Mar 2016 20:21:22 -0600 [thread overview]
Message-ID: <CAOkr1zUutTw5o20OaVG74q8Mf9eXF=bABbMhpdDN-dAAoaajBg@mail.gmail.com> (raw)
In-Reply-To: <20160322011111.GH1619@mcvoy.com>
I recall Grove's book, High Output Management. And, the companion book,
written by employees: Dealing With High Output Management.
On Mon, Mar 21, 2016 at 7:11 PM, Larry McVoy <lm at mcvoy.com> wrote:
> https://newsroom.intel.com/news-releases/andrew-s-grove-1936-2016/
>
> I know some of the processor people at intel and I was looking around,
> found this, interesting read if you are into the history:
>
> http://people.cs.clemson.edu/~mark/330/chronques.html
>
> For those that don't know, Colwell did the P6 pipeline, I think under
> Groove or right after Groove got cancer. There was P5, then P6, then
> they did a different pipeline that they called Pentium 4 (made no sense
> to me but their names never do). The Pentium 4 was the one where
> they speculated on what the answer would be for some instructions.
> As in you could do a load and they'd guess that it was zero or not.
> They were going for great clock rate, and they got it, but they also
> got instructions that would take 2000 cycles to get through.
>
> That pipeline got booted and so far as I know, the Colwell P6 pipeline
> lives on in every Intel processor after the Pentium 4.
>
> Getting back to Andy, I loved his time as CEO, I think he did a lot of
> good for that company. Here's to him!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160321/97a9a175/attachment.html>
next prev parent reply other threads:[~2016-03-22 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 1:11 Larry McVoy
2016-03-22 2:21 ` Marc Rochkind [this message]
2016-03-22 13:38 ` Nelson H. F. Beebe
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='CAOkr1zUutTw5o20OaVG74q8Mf9eXF=bABbMhpdDN-dAAoaajBg@mail.gmail.com' \
--to=rochkind@basepath.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).