9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] new lguest port available
Date: Wed, 23 Apr 2008 20:24:33 -0500	[thread overview]
Message-ID: <a4e6962a0804231824n3cd281a5o5cae5fc9a8a7a844@mail.gmail.com> (raw)
In-Reply-To: <22dab4d01b21fbbb552e41444d65fa6d@quanstro.net>

On Wed, Apr 23, 2008 at 7:53 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>
>  what i'm saying is boils down to 10ms + 100ns  is essentially 10ms.
>  so it's slower, but at a level a couple (or three) orders of magnitude too
>  low to be very significant.
>

ah, but its not always 10ms because of the page cache...but I'm
digressing to a new low level.  Actually,  the argument that Ron and I
both made is that they should ditch both the network and the block
(and the console) drivers/protocols and just use 9p for all three.  It
adds your slight 100ns of overhead, but unifies all God's children.
However, given that the virtio stuff is infinitely better than the Xen
approach and the other craptastic virtualization I/O schemes, we
decided to leave well enough alone and do the 9p stuff ourselves
(which begs the question why Ron is using the disk and net drivers and
not the superior 9p driver, but I digress yet again).

>  > [...] adding extra layers for nothing.
>
>  avoiding maintaing a second interface doesn't count?  and according
>  to ron, the network is fast right now.  this virtual ata interface isn't.
>

come back to his jebus and remember that the only real goal of all
virtualization people is to support windows -- they'll always have a
block device.  It will get faster, you can hear the millions of
monkey's typing in the distance.

>
>  now i'm really dreaming but ... why don't you convince the virtualizer guys
>  to implement aoe instead of a straight ata interface for high performance.
>  it would be less work for them too, and would eliminate the extra layer --
>  vblade.
>

I misled you a bit when I said it was AOV, its actually much closer to
just the straight block device.  No real naming issues and it
back-ends into a bunch of stuff they want like copy-on-write and what
not.  WAIT - I already hear you complaining about my lack of
consistency because I was talking about kernel-cut-thru's -- however,
the nature of the game is there are several back-ends for several
different solutions.  I like AOE, I think its a great general
solution, but I don't see it solving their problems and it complicates
some of their security, failover and migration schemes.  Its close to
the equivalent of saying why doesn't Linux use AOE as its block driver
interface.

          -eric


      reply	other threads:[~2008-04-24  1:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23 18:01 ron minnich
2008-04-23 18:10 ` Eric Van Hensbergen
2008-04-24 16:21   ` ron minnich
2008-04-23 19:21 ` Juan M. Mendez
2008-04-23 20:30   ` Stefan Hajnoczi
2008-04-23 22:56   ` ron minnich
2008-04-23 23:00     ` ron minnich
2008-04-23 23:22     ` erik quanstrom
2008-04-23 23:40       ` ron minnich
2008-04-23 23:55         ` erik quanstrom
2008-04-24  0:11       ` Eric Van Hensbergen
2008-04-24  0:29         ` erik quanstrom
2008-04-24  0:40           ` Eric Van Hensbergen
2008-04-24  0:53             ` erik quanstrom
2008-04-24  1:24               ` Eric Van Hensbergen [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=a4e6962a0804231824n3cd281a5o5cae5fc9a8a7a844@mail.gmail.com \
    --to=ericvh@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).