From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3e1162e60807312018p4f0c1e58s7c76b3d1980dc97f@mail.gmail.com> Date: Thu, 31 Jul 2008 20:18:28 -0700 From: "David Leimbach" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <13426df10807311732x4dd1fc19y925aa01a130df15d@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_101721_7458514.1217560708077" References: <663f5719ee9996a16c5972fc132e54ca@terzarima.net> <20080731231944.318CB5B57@mail.bitblocks.com> <13426df10807311732x4dd1fc19y925aa01a130df15d@mail.gmail.com> Subject: Re: [9fans] mmap Topicbox-Message-UUID: f995b3cc-ead3-11e9-9d60-3106f5b1d025 ------=_Part_101721_7458514.1217560708077 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Jul 31, 2008 at 5:32 PM, ron minnich wrote: > here is a thought: > > the kernel does mmap for code/data. This is because we think of a file > as a segment of data that somehow maps well to a segment of memory. > > You wouldn't execute code from a stream, now, would you? > > Well, this: http://www.ambric.com/ > > has hardware channels. And you can > call from channel > and execute code being sent down a channel to you from another cpu. > > There's no real analogue to this in any OS I've used for a while ... > > You could write the mcilroy sieve in this very directly. You could > even, when starting a new thread, push the code down to the next cpu. > And that cpu is paused in a call from channel until it gets its code. > A nice way to keep them idle until you need them. > > it's a very interesting architecture, to say the least. For me anyway > the most novel thing I've seen in a while. > The ARM 7 and ARM 9 procs in the Nintendo DS can talk back and forth via a FIFO at a pretty low level :-) http://www.double.co.nz/nintendo_ds/nds_develop7.html Dave > > ron > > ------=_Part_101721_7458514.1217560708077 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline


On Thu, Jul 31, 2008 at 5:32 PM, ron minnich <rminnich@gmail.com> wrote:
here is a thought:

the kernel does mmap for code/data. This is because we think of a file
as a segment of data that somehow maps well to a segment of memory.

You wouldn't execute code from a stream, now, would you?

Well, this: http://www.ambric.com/

has hardware channels. And you can
call from channel
and execute code being sent down a channel to you from another cpu.


There's no real analogue to this in any OS I've used for a while ...

You could write the mcilroy sieve in this very directly. You could
even, when starting a new thread, push the code down to the next cpu.
And that cpu is paused in a call from channel until it gets its code.
A nice way to keep them idle until you need them.

it's a very interesting architecture, to say the least. For me anyway
the most novel thing I've seen in a while.

The ARM 7 and ARM 9 procs in the Nintendo DS can talk back and forth via a FIFO at a pretty low level :-)

http://www.double.co.nz/nintendo_ds/nds_develop7.html

Dave 

ron


------=_Part_101721_7458514.1217560708077--