From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] mmap
Date: Thu, 31 Jul 2008 20:18:28 -0700 [thread overview]
Message-ID: <3e1162e60807312018p4f0c1e58s7c76b3d1980dc97f@mail.gmail.com> (raw)
In-Reply-To: <13426df10807311732x4dd1fc19y925aa01a130df15d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
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
>
>
[-- Attachment #2: Type: text/html, Size: 1931 bytes --]
next prev parent reply other threads:[~2008-08-01 3:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 14:24 mmap Russ Cox
2008-07-17 14:34 ` [9fans] mmap erik quanstrom
2008-07-29 8:52 ` Enrico Weigelt
2008-07-29 9:45 ` Charles Forsyth
2008-07-29 15:04 ` Alexander Sychev
2008-07-29 15:19 ` erik quanstrom
2008-07-29 15:35 ` ron minnich
2008-07-29 15:46 ` Roman V. Shaposhnik
2008-07-29 15:35 ` David Leimbach
2008-07-29 16:28 ` Venkatesh Srinivas
2008-07-29 16:55 ` Charles Forsyth
2008-07-29 17:08 ` Charles Forsyth
2008-07-30 16:36 ` Roman V. Shaposhnik
2008-07-30 17:02 ` Paul Lalonde
2008-07-31 21:39 ` Charles Forsyth
2008-07-31 23:19 ` Bakul Shah
2008-08-01 0:32 ` ron minnich
2008-08-01 3:18 ` David Leimbach [this message]
2008-08-02 13:22 ` Richard Miller
2008-08-02 16:10 ` ron minnich
2008-08-02 19:12 ` Richard Miller
2008-07-31 8:51 ` Paweł Lasek
[not found] ` <20080729162639.GA31092@satori.no-ip.org>
2008-07-30 15:29 ` Enrico Weigelt
2008-07-30 15:43 ` Roman V. Shaposhnik
2008-11-03 0:22 ` Enrico Weigelt
2008-07-30 16:25 ` Joel C. Salomon
2008-07-30 17:28 ` Kernel Panic
2008-07-30 18:26 ` erik quanstrom
2008-07-31 1:42 ` Joel C. Salomon
2008-11-03 0:50 erik quanstrom
2008-11-03 1:36 ` ron minnich
2008-11-03 6:29 ` Charles Forsyth
2008-11-03 6:58 ` ron minnich
2008-11-03 7:50 ` Bruce Ellis
2008-11-04 4:43 ` Enrico Weigelt
2008-11-04 7:15 ` Andrew Simmons
2008-11-04 8:01 ` Bakul Shah
2008-11-04 14:13 ` Charles Forsyth
2008-11-10 23:15 ` gas
2008-11-04 16:02 ` ron minnich
2008-11-04 18:19 ` Kim Shrier
2008-11-04 16:09 ` David Leimbach
[not found] <1d371286c515cad580f68eddbe2cdf57@quanstro.net>
2008-11-03 3:18 ` Enrico Weigelt
2008-11-03 3:31 ` ron minnich
2008-11-03 6:27 ` Charles Forsyth
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=3e1162e60807312018p4f0c1e58s7c76b3d1980dc97f@mail.gmail.com \
--to=leimy2k@gmail.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).