From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Symlinking /usr/portage/distfiles
Date: Thu, 1 Feb 2007 11:10:40 +0200 [thread overview]
Message-ID: <200702011110.40934.alan@linuxholdings.co.za> (raw)
In-Reply-To: <3D60AF2712C16D42A38076E52FD6E3D23F0D70@ukmcrdembx01.rd.astrazeneca.net>
On Thursday 01 February 2007, Nelson, David (ED, PAR&D) wrote:
> > Also Pentium-M has a lower latency L2 cache than P-4. With respect
> > to pipeline lengths I was curious to see what they actually
> > were: P-4 has
> > 20 stages, P-M has.. err... < 20 stages (Intel won't say exactly!).
> >
> > I found this an interesting read for those of you interested in
> > this:
> >
> > http://www.anandtech.com/cpuchipsets/showdoc.aspx?i=2342&p=1
> >
> > Cheers
> >
> > Mark
>
> At the risk of pulling this topic a little more off-topic - the P-M
> vs P-4 is an interesting case of a Pentium 3 chipset with a die
> shrink outperforming a P-4.
>
> The Intel Core (2) Solo/Duo CPUs are based on the Pentium M as well.
> Netburst is pretty much dead afaik.
Thanks for everyone's replies. I now know, 6 months later, exactly what
cpu I have :-)
I've been finding over the last 10 years or so that if I don't keep up
with new cpu developments, it takes ages to get familiar with the
terminology and current products again. I think it's called "the price
of rapid technology advances"
alan
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-02-01 9:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 13:16 [gentoo-user] Symlinking /usr/portage/distfiles Vlad Dogaru
2007-01-27 13:29 ` Mick
2007-01-27 13:31 ` Dale
2007-01-27 16:40 ` Vlad Dogaru
2007-01-27 18:14 ` Jürgen Geuter
2007-01-27 19:05 ` Jeffrey Rollin
2007-01-27 19:52 ` Vlad Dogaru
2007-01-27 23:48 ` Neil Bothwick
2007-01-29 7:38 ` Alan McKinnon
2007-01-29 13:20 ` Albert Hopkins
[not found] ` <200701292112.22080.alan@linuxholdings.co.za>
2007-01-30 9:29 ` Neil Bothwick
2007-01-30 12:22 ` Bo Ørsted Andresen
2007-01-30 13:09 ` Neil Bothwick
2007-01-30 12:59 ` Albert Hopkins
2007-01-30 7:25 ` Bo Ørsted Andresen
[not found] ` <200701301422.12957.bo.andresen@zlin.dk>
[not found] ` <200701301552.37737.alan@linuxholdings.co.za>
2007-01-30 14:06 ` Uwe Thiem
2007-01-31 11:02 ` Alan McKinnon
2007-01-31 12:22 ` Uwe Thiem
2007-01-31 12:34 ` Bo Ørsted Andresen
2007-01-31 13:23 ` Alan McKinnon
2007-01-31 13:22 ` Alan McKinnon
2007-01-31 13:38 ` Bo Ørsted Andresen
2007-01-31 15:58 ` Alan McKinnon
2007-01-31 19:13 ` Boyd Stephen Smith Jr.
2007-01-31 23:49 ` Mark Kirkwood
2007-02-01 8:51 ` Nelson, David (ED, PAR&D)
2007-02-01 9:10 ` Alan McKinnon [this message]
2007-02-01 18:43 ` Ralf Stephan
2007-02-01 20:41 ` Dan Farrell
2007-01-30 14:35 ` Neil Bothwick
2007-01-30 16:26 ` Anthony E. Caudel
2007-01-31 11:16 ` Alan McKinnon
2007-01-31 12:25 ` Dan Farrell
2007-02-01 10:30 ` Neil Bothwick
2007-01-31 15:22 ` Anthony E. Caudel
2007-01-30 19:10 ` Mick
2007-01-30 19:31 ` Neil Bothwick
2007-01-30 20:18 ` Albert Hopkins
2007-01-30 22:39 ` Neil Bothwick
2007-01-31 0:45 ` Steve Dibb
2007-01-31 1:22 ` Neil Bothwick
2007-01-31 10:37 ` Boyd Stephen Smith Jr.
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=200702011110.40934.alan@linuxholdings.co.za \
--to=alan@linuxholdings.co.za \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox