From: Roman Shaposhnik <rvs@sun.com>
To: weigelt@metux.de,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] OLE vs. 9P
Date: Thu, 10 Jan 2008 12:45:53 -0800 [thread overview]
Message-ID: <1199997953.4308.475.camel@work.sfbay.sun.com> (raw)
In-Reply-To: <20080110021656.GA26347@nibiru.local>
On Thu, 2008-01-10 at 03:16 +0100, Enrico Weigelt wrote:
> > The trickiest part seems to be exploring locality for the mapped
> > rendering (imagine a multimedia plugin displaying an HD movie).
>
> Those things require special interfaces, which tunnel streams
> through 9P. Maybe something like mjpeg with timestamps.
I don't think tunneling will get you very far. In this particular
case you really need to exploit locality and get to do DMA to the
device or the like. The tricky portion is arbitrating such resources.
Thanks,
Roman.
prev parent reply other threads:[~2008-01-10 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 18:44 Enrico Weigelt
2008-01-07 20:14 ` Roman Shaposhnik
2008-01-08 18:31 ` Enrico Weigelt
2008-01-09 20:46 ` Roman Shaposhnik
2008-01-10 2:16 ` Enrico Weigelt
2008-01-10 10:36 ` Sergey Zhilkin
2008-01-11 0:54 ` Enrico Weigelt
2008-01-10 20:45 ` Roman Shaposhnik [this message]
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=1199997953.4308.475.camel@work.sfbay.sun.com \
--to=rvs@sun.com \
--cc=9fans@cse.psu.edu \
--cc=weigelt@metux.de \
/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).