9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sam Watkins <sam@nipl.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Barrelfish
Date: Tue, 20 Oct 2009 03:34:56 +1100	[thread overview]
Message-ID: <20091019163456.GF13857@nipl.net> (raw)
In-Reply-To: <d070dc0f7dba4b42cd971e5f8edaeda3@ladd.quanstro.net>

On Mon, Oct 19, 2009 at 12:05:19PM -0400, erik quanstrom wrote:
> > Details of the calculation: 7200 seconds * 30fps * 12*16 (50*50 pixel
> > chunks) * 500000 elementary arithmetic/logical operations in a pipeline
> > (unrolled).  7200*30*12*16*500000 = 20 trillion (20,000,000,000,000)
> > processing units.  This is only a very rough estimate and does not consider
> > all the issues.
>
> could you do a similar calcuation for the memory bandwidth required to
> deliver said instructions to the processors?

The "processors" (actually smaller processing units) would mostly be configured
at load time, much like an FPGA.  Most units would execute a single simple
operation repeatedly on streams of data, they would not read instructions and
execute them sequentially like a normal CPU.

The data would travel through the system step by step, it would mostly not need
to be stored in RAM.  If some RAM was needed, it would be small amounts on
chip, at appropriate places in the pipeline.

Some programs (not so much video encoding I think) do need a lot of RAM for
intermediate calculations, or IO for example to fetch stuff from a database.
Such systems can also be designed as networks of simple processing units
connected by data streams / pipelines.

Sam



  reply	other threads:[~2009-10-19 16:34 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<20091019155738.GB13857@nipl.net>
2009-10-19 16:05 ` erik quanstrom
2009-10-19 16:34   ` Sam Watkins [this message]
2009-10-19 17:30     ` ron minnich
2009-10-19 17:57       ` W B Hacker
2009-10-19 18:14       ` David Leimbach
     [not found] <<4ADD147A.4090801@maht0x0r.net>
2009-10-20  2:11 ` erik quanstrom
2009-10-20  2:33   ` matt
     [not found] <<20091019182352.GA1688@polynum.com>
2009-10-19 18:48 ` erik quanstrom
     [not found] <<4ADC7439.3060502@maht0x0r.net>
2009-10-19 16:13 ` erik quanstrom
2009-10-19 18:23   ` tlaronde
2009-10-20  1:38   ` matt
2009-10-20  1:58     ` Eris Discordia
2009-10-20  2:17       ` matt
     [not found] <<20091018031508.717CE5B30@mail.bitblocks.com>
2009-10-19 13:44 ` erik quanstrom
2009-10-19 14:36   ` David Leimbach
     [not found] <<d50d7d460910161417w45b5c675p8740315aaf6861f@mail.gmail.com>
2009-10-16 22:25 ` erik quanstrom
     [not found] <<20091016172030.GB3135@nipl.net>
2009-10-16 18:34 ` erik quanstrom
     [not found] <<3e1162e60910150805q2ea3f682w688299a39274051c@mail.gmail.com>
2009-10-15 15:28 ` erik quanstrom
     [not found] <<4AD70EE9.1010208@conducive.org>
2009-10-15 13:52 ` erik quanstrom
     [not found] <<207092dc429fe476c2046d537aeaa400@hamnavoe.com>
2009-10-15 13:52 ` erik quanstrom
2009-10-15 15:07   ` David Leimbach
2009-10-15 15:21     ` roger peppe
2009-10-16 17:21       ` Sam Watkins
2009-10-16 23:39         ` Nick LaForge
2009-10-18  1:12         ` Roman Shaposhnik
2009-10-19 14:14           ` matt
2009-10-19 16:00           ` Sam Watkins
     [not found] <<20091015105328.GA18947@nipl.net>
2009-10-15 13:27 ` erik quanstrom
2009-10-15 13:40   ` Richard Miller
2009-10-16 17:20   ` Sam Watkins
2009-10-16 18:18     ` Latchesar Ionkov
2009-10-19 15:26       ` Sam Watkins
2009-10-19 15:33         ` andrey mirtchovski
2009-10-19 15:50         ` ron minnich
2009-10-16 21:17     ` Jason Catena
2009-10-17 20:58       ` Dave Eckhardt
2009-10-18  2:09         ` Jason Catena
2009-10-18 16:02           ` Dave Eckhardt
2009-10-17 18:45   ` Eris Discordia
2009-10-17 21:07     ` Steve Simon
2009-10-17 21:18       ` Eric Van Hensbergen
2009-10-18  8:48         ` Eris Discordia
2009-10-18  8:44       ` Eris Discordia
2009-10-19 15:57     ` Sam Watkins
2009-10-19 16:03       ` ron minnich
2009-10-19 16:46       ` Russ Cox
2009-10-20  2:16       ` matt
2009-10-20  9:15         ` Steve Simon
2009-10-21 15:43         ` Sam Watkins
2009-10-21 16:11           ` Russ Cox
2009-10-21 16:37             ` Sam Watkins
2009-10-21 18:01           ` ron minnich
2009-10-28 15:37           ` matt
     [not found]   ` <A90043D02D52B2CBF2804FA4@192.168.1.2>
2009-10-18  0:06     ` ron minnich
2009-10-18  0:54       ` Roman Shaposhnik
2009-10-14 19:09 Tim Newsham
2009-10-14 19:54 ` Roman Shaposhnik
2009-10-14 21:21   ` Tim Newsham
2009-10-14 21:33     ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2009-10-14 21:42       ` Noah Evans
2009-10-14 21:45         ` erik quanstrom
2009-10-14 21:57           ` Noah Evans
2009-10-14 22:10         ` Eric Van Hensbergen
2009-10-14 22:21           ` Noah Evans
2009-10-15  1:03     ` David Leimbach
2009-10-15  1:50     ` Roman Shaposhnik
2009-10-15  2:12       ` Eric Van Hensbergen
2009-10-15 10:53       ` Sam Watkins
2009-10-15 11:50         ` Richard Miller
2009-10-15 12:00           ` W B Hacker
2009-10-16 17:03           ` Sam Watkins
2009-10-16 18:17             ` ron minnich
2009-10-16 18:39               ` Wes Kussmaul
2009-10-17 12:42             ` Roman Shaposhnik
2009-10-15 11:56         ` Josh Wood
2009-10-15 13:11         ` hiro
2009-10-15 15:05           ` David Leimbach
2009-10-18  1:15         ` Roman Shaposhnik
2009-10-18  3:15           ` Bakul Shah
     [not found]             ` <e763acc10910180606q1312ff7cw9a465d6af39c0fbe@mail.gmail.com>
2009-10-18 13:22               ` Roman Shaposhnik
2009-10-18 19:18                 ` Bakul Shah
2009-10-18 20:12                   ` ron minnich
2009-10-14 21:36   ` Eric Van Hensbergen
2009-10-15  2:05     ` Roman Shaposhnik
2009-10-15  2:17       ` Eric Van Hensbergen
2009-10-15  3:32         ` Tim Newsham
2009-10-15  3:59           ` Eric Van Hensbergen
2009-10-15 17:39             ` Tim Newsham
2009-10-15 18:28 ` Christopher Nielsen
2009-10-15 18:55   ` W B Hacker

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=20091019163456.GF13857@nipl.net \
    --to=sam@nipl.net \
    --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).