From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] From our "not quite grasping the concept" file
Date: Thu, 8 Nov 2007 10:20:04 -0500 [thread overview]
Message-ID: <d01ef9b15d233274878ff8e61f760a9a@quanstro.net> (raw)
In-Reply-To: <a4e6962a0711080455tb135bdam4f7127b5f4feb543@mail.gmail.com>
> The opportunity still exists -- only one driver needs to implement
> their numeric hack - 9p. Then the rest can be based off of that.
> Unfortunately, evolution just comes slow and painful.
>
> -eric
are 9p mesages really the right vehicle for this? 9p messages
provides a serialized and in a standard byte order. this requires
byte reordering (on intel) and copying. but are these really needed?
the guest and host are on the same platform, so the guest can
pass pointers to the host. for the same reason, integers don't need
reformatting.
modern devices usually dma directly, so the host may never need
to touch the pointed-to memory.
perhaps using Fcall structures directly would be more efficient?
- erik
next prev parent reply other threads:[~2007-11-08 15:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 7:31 ron minnich
2007-11-08 12:00 ` Richard Miller
2007-11-08 12:55 ` Eric Van Hensbergen
2007-11-08 15:20 ` erik quanstrom [this message]
2007-11-08 16:07 ` Latchesar Ionkov
2007-11-08 16:38 ` erik quanstrom
2007-11-08 17:24 ` Latchesar Ionkov
2007-11-08 16:10 ` Eric Van Hensbergen
2007-11-08 16:33 ` erik quanstrom
2007-11-08 16:42 ` ron minnich
2007-11-08 16:51 ` roger peppe
2007-11-08 13:57 ` erik quanstrom
2007-11-08 19:46 ` Pietro Gagliardi
2007-11-09 1:07 ` dave.l
2007-11-09 4:43 ` Paul Lalonde
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=d01ef9b15d233274878ff8e61f760a9a@quanstro.net \
--to=quanstro@quanstro.net \
--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).