From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Multimedia on Plan 9
Date: Fri, 22 Jun 2007 17:07:00 -0400 [thread overview]
Message-ID: <50ffb060d0e6fe7eaf82a7bc15c68424@coraid.com> (raw)
In-Reply-To: <1182544572.25089.378.camel@work.sfbay.sun.com>
> Although Plan9 file model, as nice as it is breaks horribly when
> we start talking about HD multimedia content. The performance bottleneck
> is quite noticeable at 50MBpbs :-(
50 MB/s == 1 gigabit
i think this will be a problem as soon as there exist gigabit link to actual
content providers.
- erik
next prev parent reply other threads:[~2007-06-22 21:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 18:19 Anant Narayanan
2007-06-21 21:30 ` Charles Forsyth
2007-06-21 22:53 ` Jack Johnson
2007-06-22 0:10 ` Roman Shaposhnick
2007-06-22 9:01 ` Richard Miller
2007-06-22 9:15 ` vir
2007-06-22 9:52 ` Steve Simon
2007-06-22 20:36 ` Roman Shaposhnick
2007-06-22 20:41 ` Lyndon Nerenberg
2007-06-22 21:07 ` erik quanstrom [this message]
2007-06-22 22:58 ` Roman Shaposhnick
2007-06-22 20:24 ` Roman Shaposhnick
2007-06-22 0:15 ` Roman Shaposhnick
2007-06-22 0:19 ` Roman Shaposhnick
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=50ffb060d0e6fe7eaf82a7bc15c68424@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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).