From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] NUMA
Date: Fri, 15 Jul 2011 22:21:57 +0200 [thread overview]
Message-ID: <20110715202157.GA5157@polynum.com> (raw)
In-Reply-To: <20110715151535.GA2405@polynum.com>
On Fri, Jul 15, 2011 at 05:15:35PM +0200, tlaronde@polynum.com wrote:
>[...]
> Writing down an explanation about the differences between the on file
> saved version, and the runtime structures, I wrote that portable was for
> sharing between whatever CPU architectures, while the in memory was
> fitting a particular architecture because the memory is tightly coupled
> to the cores and not shar... Oups! Hence the question.
Thinking about it a little more, whether the whole process memory is
migrated, that is not only "data" but instructions; in this case, the
new CPU processing has to understand the whole (natively or by
emulation) and in this case the program can "ignore" what's going on.
Or if the data is separated and shared, it has to be made "portable", by
whatever mean but known to the programmer and/or to the binary tools.
Well, I don't know if this is totally or only partially stupid. But this
was just an "en passant" question. Sorry for the noise. Back to work...
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2011-07-15 20:21 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 [this message]
2011-07-15 20:47 ` ron minnich
2011-07-15 22:59 ` Charles Forsyth
2011-07-16 8:02 ` tlaronde
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=20110715202157.GA5157@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).