From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] GCC/G++: some stress testing
Date: Tue, 4 Mar 2008 10:00:50 -0800 [thread overview]
Message-ID: <1204653650.27006.322.camel@goose.sun.com> (raw)
In-Reply-To: <9f3897940803040257i67b7b8ccp3e60eb1b1236d5a8@mail.gmail.com>
On Tue, 2008-03-04 at 11:57 +0100, Paweł Lasek wrote:
> > I take it that you really do mean "simultaneous". As in: you actually
> > have hundreds of cores available on the same system. I'm actually
> > quite curious to find out what's the highest number of cores available
> > of a single shared memory systems that you, or anybody else has
> > experienced in practice so far (mine would be 32 == 8 CPUs x 4 cores AMD
> > Barcelona)? Now even more important question is -- what are the
> > expectations for, this number in 5 years from now?
> >
>
> Actually, with parts available from AMD you can directly mesh up to 64
> sockets, each with (currently) 4 cores, 8 core cpu announced (as MCP
> in the beginning). And there were available methods for routing HT
> traffic with number of sockets nearing thousands or tens of thousands.
> Dunno if they used it directly with cache coherency protocol though.
Understood. Although, what I meant was a practical hands-on experience.
So that the war stories can be told. Otherwise, on the SPARC side, I'd
be able to claim 128 in Sun's M9000.
Thanks,
Roman.
next prev parent reply other threads:[~2008-03-04 18:00 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 4:55 lucio
2008-03-01 6:02 ` Eric Van Hensbergen
2008-03-01 6:25 ` lucio
2008-03-01 6:39 ` Lyndon Nerenberg
2008-03-01 6:52 ` lucio
2008-03-01 6:59 ` Lyndon Nerenberg
2008-03-01 7:42 ` lucio
2008-03-01 7:56 ` Lyndon Nerenberg
2008-03-01 7:11 ` ron minnich
2008-03-01 7:29 ` Lyndon Nerenberg
2008-03-01 16:40 ` ron minnich
2008-03-01 16:50 ` Bruce Ellis
2008-03-01 8:14 ` lucio
2008-03-01 11:13 ` hiro
2008-03-01 11:47 ` [9fans] intellect? Lyndon Nerenberg
2008-03-01 11:51 ` Lyndon Nerenberg
2008-03-01 11:53 ` Charles Forsyth
2008-03-01 12:11 ` hiro
2008-03-01 12:37 ` hiro
2008-03-01 16:22 ` [9fans] GCC/G++: some stress testing Eric Van Hensbergen
2008-03-01 7:12 ` ron minnich
2008-03-01 7:32 ` Lyndon Nerenberg
2008-03-01 11:49 ` Charles Forsyth
2008-03-01 11:58 ` lucio
2008-03-01 18:15 ` don bailey
2008-03-01 18:24 ` erik quanstrom
2008-03-01 20:19 ` lucio
2008-03-01 21:36 ` ron minnich
2008-03-02 1:07 ` Paul Lalonde
2008-03-02 4:28 ` ron minnich
2008-03-02 8:03 ` Bruce Ellis
2008-03-02 11:12 ` Charles Forsyth
2008-03-02 16:21 ` Paul Lalonde
2008-03-02 18:59 ` erik quanstrom
2008-03-02 20:34 ` Paul Lalonde
2008-03-02 22:00 ` Philippe Anel
2008-03-03 3:19 ` ron minnich
2008-03-03 9:12 ` Philippe Anel
2008-03-03 3:25 ` Paul Lalonde
2008-03-03 9:12 ` Philippe Anel
2008-03-04 2:31 ` Paul Lalonde
2008-03-03 3:31 ` Roman V. Shaposhnik
2008-03-04 0:49 ` erik quanstrom
2008-03-04 2:17 ` Paul Lalonde
2008-03-04 4:52 ` erik quanstrom
2008-03-04 10:57 ` Paweł Lasek
2008-03-04 14:57 ` ron minnich
2008-03-04 15:55 ` Philippe Anel
2008-03-04 18:27 ` ron minnich
2008-03-04 18:00 ` Roman V. Shaposhnik [this message]
2008-03-07 5:21 ` lucio
2008-03-07 10:21 ` Russ Cox
2008-03-07 11:15 ` Pietro Gagliardi
2008-03-07 18:49 ` Skip Tavakkolian
2008-03-07 18:55 ` lucio
2008-03-07 17:22 ` lucio
2008-03-01 14:45 ` lejatorn
2008-03-01 14:49 ` Pietro Gagliardi
2008-03-01 15:17 ` lucio
2008-03-01 16:35 ` Pietro Gagliardi
2008-03-01 16:41 ` ron minnich
2008-03-01 16:53 ` Bruce Ellis
2008-03-01 17:13 ` ron minnich
2008-03-01 20:29 ` geoff
2008-03-01 21:36 ` ron minnich
2008-03-01 22:29 ` Bruce Ellis
2008-03-04 7:35 ` Lyndon Nerenberg
2008-03-01 15:02 ` lucio
2008-03-01 16:31 ` Eric Van Hensbergen
2008-03-01 17:52 ` lejatorn
2008-03-02 17:57 ` sqweek
2008-03-02 18:22 ` lucio
2008-03-02 20:56 ` cinap_lenrek
2008-03-09 17:53 Aharon Robbins
2008-03-09 17:57 ` Bruce Ellis
2008-03-09 18:28 ` Pietro Gagliardi
2008-03-09 19:17 ` erik quanstrom
2008-03-09 19:22 ` Skip Tavakkolian
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=1204653650.27006.322.camel@goose.sun.com \
--to=rvs@sun.com \
--cc=9fans@cse.psu.edu \
/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).