9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] From our "not quite grasping the concept" file
Date: Thu,  8 Nov 2007 11:33:12 -0500	[thread overview]
Message-ID: <1d8207a7813237f3f1241e0c5a274228@coraid.com> (raw)
In-Reply-To: <a4e6962a0711080810q5b32a487nc25b5ec6be79037@mail.gmail.com>

> > 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.
> >
> 
> 9p is the right organizational structure.  The details of marshalling
> and pass-by-copy versus pass-by-reference are transport issues.  Lucho
> and I have been playing with zero-marhsalling/zero-copy transport
> variants of 9P for virtualized environments.
> 
>           -eric

perhaps i'm being too pedantic, but 9p is defined by how it marshals data.

- erik


  reply	other threads:[~2007-11-08 16:33 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
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 [this message]
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=1d8207a7813237f3f1241e0c5a274228@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).