9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] NUMA
Date: Sat, 16 Jul 2011 10:02:47 +0200	[thread overview]
Message-ID: <20110716080247.GA394@polynum.com> (raw)
In-Reply-To: <CAP6exYK6da_9mVsbRhXf0x-PzUqGFDn4oxK5UE4fCxq31j7RxA@mail.gmail.com>

On Fri, Jul 15, 2011 at 01:47:40PM -0700, ron minnich wrote:
> http://supertech.csail.mit.edu/porch/
> 
> long ago, but I saw it checkpoint between x86 and sparc.

Thanks for the pointer!

At least it shows that it is always useful to write down the
"axiomatics" of one code, since making explicit the assumptions that
were only implicit can rise questions.

Some time ago, reading about "what makes parallel programming
difficult", I discover that all in all the problems arise when a
sequence of instructions is not "prédicative" in Poincaré's definition,
i.e. "is [predicative] an on-going classification that is not disrupted
by the adjunction of new elements".

The Itanium story, as guessed early by Hennessy and Patterson in
"Computer Architecture", shows that efficiency relying on too
complex knowledge, asking too much to the programmers and the
compilers, is likely to fail.

On the other hand, if the programmer doesn't think at all about these
problems, distributed and parallel systems will have hard times and
limits and can't do wonders with "spaghetti" code.

What is the minimal hints the programmer shall give? At least
predicativity. I wonder what minimum set of keywords could be added,
say, to C, so that the situation can be greatly improved without the
burden being greatly increased. [non-predicative routines being, from
a parallel point of view, atomic]

-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C




  parent reply	other threads:[~2011-07-16  8:02 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15 15:15 tlaronde
2011-07-15 20:21 ` tlaronde
2011-07-15 20:47   ` ron minnich
2011-07-15 22:59     ` Charles Forsyth
2011-07-16  8:02     ` tlaronde [this message]
2011-07-16 16:27       ` erik quanstrom
2011-07-16 18:06         ` tlaronde
2011-07-16 19:29           ` Ethan Grammatikidis
2011-07-16 19:54           ` erik quanstrom
2011-07-16 20:56             ` dexen deVries
2011-07-16 22:10               ` Charles Forsyth
2011-07-17  1:44                 ` erik quanstrom
2011-07-17  7:38                   ` tlaronde
2011-07-17  8:44                     ` Bakul Shah
2011-07-17 10:02                       ` tlaronde
2011-07-17 12:04                         ` dexen deVries
2011-07-17 15:24                       ` erik quanstrom
2011-07-17 15:28                         ` ron minnich
     [not found]                         ` <CAP6exYL2DJXbKfPZ8+D5uL=fRWKEyr8vY2OVc4NTO3wsFo=Unw@mail.gmail.c>
2011-07-17 15:32                           ` erik quanstrom
2011-07-17 17:16                         ` Bakul Shah
2011-07-17 17:21                           ` erik quanstrom
2011-07-17 15:51                     ` erik quanstrom
2011-07-17 16:12                       ` dexen deVries
2011-07-17 16:37                       ` tlaronde
2011-07-17 10:08               ` Ethan Grammatikidis
2011-07-17 14:50                 ` erik quanstrom
2011-07-17 17:01                   ` Ethan Grammatikidis
2011-07-17  3:39       ` Joel C. Salomon
2011-07-17  7:01         ` tlaronde
2011-07-17 15:05           ` Joel C. Salomon
2011-07-17 15:26           ` erik quanstrom
2011-07-17 15:52             ` ComeauAt9Fans@gmail.com

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=20110716080247.GA394@polynum.com \
    --to=tlaronde@polynum.com \
    --cc=9fans@9fans.net \
    /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).