From: Jonathan Roewen <jonathan.roewen@gmail.com>
To: skaller <skaller@users.sourceforge.net>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] The Bytecode Interpreter...
Date: Sun, 30 Oct 2005 13:41:17 +1300 [thread overview]
Message-ID: <ad8cfe7e0510291741u6f3dfbb2r33995dc3751c8f45@mail.gmail.com> (raw)
In-Reply-To: <1130599340.7560.107.camel@rosella>
> Your main problem, IMHO, will be concurrency, not interrupts.
> That is -- multiprocessor support. Because typical
> multiprocessor OS shares a lot more data between CPUs,
> and runs at least part of the kernel on ALL the CPUs.
Possibly. I think we'll tackle this by a separate kernel
instance/runtime per processor, and act like they're separate machines
.. akin to distributed programming.
But multiprocessor stuff is a long, long way off.
next prev parent reply other threads:[~2005-10-30 0:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 10:01 Jonathan Roewen
2005-10-21 11:27 ` David MENTRE
2005-10-21 22:24 ` Jonathan Roewen
2005-10-21 23:49 ` Oliver Bandel
2005-10-22 21:33 ` Jonathan Roewen
2005-10-22 0:32 ` Jon Harrop
2005-10-22 0:39 ` Jacques Garrigue
2005-10-23 1:03 ` Jonathan Roewen
2005-10-23 10:21 ` Gerd Stolpmann
2005-10-24 5:38 ` Jonathan Roewen
2005-10-24 6:13 ` Jacques Garrigue
2005-10-24 6:48 ` Jonathan Roewen
2005-10-22 0:39 ` Jonathan Roewen
2005-10-26 0:33 ` Jonathan Roewen
2005-10-26 9:56 ` Jonathan Roewen
2005-10-26 10:20 ` Jonathan Roewen
2005-10-27 14:12 ` Damien Doligez
2005-10-28 21:41 ` Jonathan Roewen
2005-10-29 11:29 ` Gerd Stolpmann
2005-10-29 15:22 ` skaller
2005-10-30 0:41 ` Jonathan Roewen [this message]
2005-11-10 10:26 ` Damien Doligez
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=ad8cfe7e0510291741u6f3dfbb2r33995dc3751c8f45@mail.gmail.com \
--to=jonathan.roewen@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=skaller@users.sourceforge.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).