From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] zettaflops workshop
Date: Thu, 25 Oct 2007 16:34:53 -0700 [thread overview]
Message-ID: <13426df10710251634s707efd62g67bbb8638949da7c@mail.gmail.com> (raw)
Some interesting preso's here:
http://www.zettaflops.org/fec07/agenda.html
More to come, I hope.
two tongue-in-cheek quotes from the workshop:
"Supernova physics: there is a lot of interest in this recently
because the fate of the universe depends on it"
and
"It's only recently that they have gotten supernovas to explode at all"
Anyway, really doing some of these simulations well is projected to
require 10^18 FLOPS.
Projection is a machine that has 2^27 CPUs ... since the Great Clock
Rate Climb is now at an end for a while, the only way to scale up is
more parallelism. One vendor contemplates memory addressabilty across
that machine, so, guess what, we just ran out of 64-bit address space,
since 2^37 bytes per CPU is not enough.
Life is getting interesting again, since you can no longer count on
clock rate increases to cover for bloatware. That's the best news.
Compact code is going to start to matter more than it has. Of course,
"compact" will start to mean "First in a 32-bit address space" but hey
...
ron
reply other threads:[~2007-10-25 23:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=13426df10710251634s707efd62g67bbb8638949da7c@mail.gmail.com \
--to=rminnich@gmail.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).