9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eris Discordia <eris.discordia@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Barrelfish
Date: Sat, 17 Oct 2009 19:45:40 +0100	[thread overview]
Message-ID: <A90043D02D52B2CBF2804FA4@[192.168.1.2]> (raw)
In-Reply-To: <4030fb6ae37f8ca8ae9c43ceefbdf57b@ladd.quanstro.net>

>> There is a vast range of applications that cannot
>> be managed in real time using existing single-core technology.
>
> please name one.

I'm a tiny fish, this is the ocean. Nevertheless, I venture: there are
already Cell-based expansion cards out there for "real-time"
H.264/VC-1/MPEG-4 AVC encoding. Meaning, 1080p video in, H.264 stream out,
"real-time." I can imagine a large market for this in broadcasting,
netcasting, simulcasting industry. Simulcasting in particular is a prime
application. Station X in Japan broadcasts a popular animated series in
1080i, while US licensor of the same content simulcasts for subscribers
through its web interface. This applies all the more to live feeds.

What seems to go ignored here is the class of embarrassingly parallel
problems which--while they may or may not be important to CS people, I
don't know--appear in many areas of applied computing. I know one person
working at an institute of the Max Planck Society who regularly runs a few
hundred instances of the same program (doing some sort of matrix
calculation for a problem in physics) with different input. He certainly
could benefit from a hundred cores inside his desktop computing platform
_if_ fitting that many cores in there wouldn't cause latencies larger than
the network latencies he currently experiences (at the moment he uses a job
manager that controls a cluster). "INB4" criticism, his input matrices are
small and his work is compute-intensive rather than memory-intensive.

Another embarrassingly parallel problem, as Sam Watkins pointed out, arises
in digital audio processing. I might add to his example of applying a
filter to sections of one track the example of applying the same or
different filters to multiple tracks at once. Multitrack editing was/is a
killer application of digital audio. Multitrack video editing, too. I
believe video/audio processing software were among the first applications
for "workstation"-class desktops that were parallelized.

By the way, I learnt about embarrassingly parallel problems from that same
Max Planck research fellow who runs embarrassingly parallel matrix
calculations.



--On Thursday, October 15, 2009 09:27 -0400 erik quanstrom
<quanstro@quanstro.net> wrote:

> On Thu Oct 15 06:55:24 EDT 2009, sam@nipl.net wrote:
>> task.  With respect to Ken, Bill Gates said something along the lines of
>> "who would need more than 640K?".
>
> on the other hand, there were lots of people using computers with 4mb
> of memory when bill gates said this.  it was quite easy to see how to use
> more than 1mb at the time.  in fact, i believe i used an apple ][ around
> that time that had ~744k.  it was a wierd amount of memory.
>
>> There is a vast range of applications that cannot
>> be managed in real time using existing single-core technology.
>
> please name one.
>
> - erik
>




  parent reply	other threads:[~2009-10-17 18:45 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
     [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] <<20091019155738.GB13857@nipl.net>
2009-10-19 16:05 ` erik quanstrom
2009-10-19 16:34   ` Sam Watkins
2009-10-19 17:30     ` ron minnich
2009-10-19 17:57       ` W B Hacker
2009-10-19 18:14       ` David Leimbach
     [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
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='A90043D02D52B2CBF2804FA4@[192.168.1.2]' \
    --to=eris.discordia@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).