From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <9f3897940803040257i67b7b8ccp3e60eb1b1236d5a8@mail.gmail.com> Date: Tue, 4 Mar 2008 11:57:15 +0100 From: "=?UTF-8?Q?Pawe=C5=82_Lasek?=" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] GCC/G++: some stress testing In-Reply-To: <1204515076.27006.173.camel@goose.sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1204515076.27006.173.camel@goose.sun.com> Topicbox-Message-UUID: 6e2ebf54-ead3-11e9-9d60-3106f5b1d025 On Mon, Mar 3, 2008 at 4:31 AM, Roman V. Shaposhnik wrote: > On Sun, 2008-03-02 at 12:34 -0800, Paul Lalonde wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > CSP doesn't scale very well to hundreds of simultaneously executing > > threads (my claim, not, as far as I've found yet, anyone else's). > > 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. -- Paul Lasek