9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Shane Morris <edgecomberts@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] GreenArrays and Plan 9/ Inferno
Date: Sun, 26 Jan 2014 14:25:37 +1100	[thread overview]
Message-ID: <CANZw+5ff=FqMbLm0BGu5bS5TFmtNxO=EBqS8q1GKbAD1Hqb-QQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]

Hello 9fans,

I saw reference to the GreenArrays chips on the list a while back, had a
look, and was mighty impressed. Then I wondered, "Exactly what does Plan 9
or Inferno have to do with these chips, and how do they relate?"

I considered you could have the 144CPU chip with mini-Styx processing
routines, which would serve my needs well - I need to move in a whole heap
of file data, process it in various ways, and move it out again, quickly,
and the promise of 90 billion instructions per second really excited me.

Obviously, these processors aren't floating point processors, and thats
fine, I'm working with moving floating point sensor readings into and out
of the "grid on a chip" and doing some basic functions on them, in a file
based format. Its just the true potential that has me going "Wow, I can see
this cloudy outline, but it still looks cool..."

I admit, I may be barking right up the wrong tree here, and if I am, I will
stand corrected. I'm just wondering of the potential of these chips,
coupled with a fast FPGA and an PCI-e x1 link to an APU running Plan 9 as a
"head node." I have a programmer who has always wanted to play with FPGAs
as a technology, and I have several books on basic VHDL. But yeah, lets not
put the cart in front of the horse now, right?

Thanks everyone!

[-- Attachment #2: Type: text/html, Size: 1505 bytes --]

                 reply	other threads:[~2014-01-26  3:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CANZw+5ff=FqMbLm0BGu5bS5TFmtNxO=EBqS8q1GKbAD1Hqb-QQ@mail.gmail.com' \
    --to=edgecomberts@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).