All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Smith <sos22-xen@srcf.ucam.org>
To: Ross Maxfield <rmaxfiel@novell.com>
Cc: xen-devel@lists.xensource.com, sos22@srcf.ucam.org
Subject: Re: RFC -  PV blk driver for hvm guest
Date: Sat, 7 Oct 2006 10:53:15 +0100	[thread overview]
Message-ID: <20061007095315.GA2111@cam.ac.uk> (raw)
In-Reply-To: <45223DA0.DD28.00D3.0@novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1357 bytes --]

> As I look further into this, an over-arching question begins to
> form.  Originally, I had suggested that a 'type=' be added to the
> 'disk' line, like the net, to indicate the use of FV or PV drivers.
> But now I'm wondering if a more global tag should be used to
> indicate that all drivers are either FV or PV.  Implementing the
> original idea would be a more involved but create the opportunity
> for one disk device to be supported by a FV driver and another by a
> PV driver.  The question is, why would anyone ever wish to have
> mixed driver technology?  With the PV drivers having such a profound
> increase in performance and given that PV drivers are available for
> the quest (and assuming if a a PV driver is available for one
> technology, i.e. LAN or BLK, then it would be available for the
> other) then why would someone use the FV driver? Thus the more
> simple solution to have a single switch in the guest's config file
> indicating the mode for all devices, LAN or BLK.
Well, it's rather handy when you're actually working on the PV
drivers, since you can e.g. have an ioemu root device and test the
block driver on some other filesystem.  Plus, if at some point in the
future we implement a PV framebuffer you're likely to have some guest
installs with BLK+LAN but not framebuffer, and so mixed mode would be
useful there.

Steven.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  parent reply	other threads:[~2006-10-07  9:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 19:21 [PATCH] [XEND] Remove hard tabs Hollis Blanchard
2006-09-21  5:58 ` Molle Bestefich
2006-09-21 20:28   ` Hollis Blanchard
2006-09-24 10:50     ` Molle Bestefich
2006-09-25 16:38       ` Hollis Blanchard
2006-09-26 15:34         ` Anthony Liguori
2006-09-25 17:07       ` Sean Dague
2006-09-27 14:07         ` Steven Rostedt
2006-09-27 21:43           ` RFC - PV blk driver for hvm guest Ross Maxfield
2006-09-27 22:26             ` Dom0 hang problem Subrahmanian, Raj
2006-09-27 22:44               ` Ian Pratt
2006-10-01 17:42             ` RFC - PV blk driver for hvm guest Steven Smith
     [not found]               ` <45223DA0.DD28.00D3.0@novell.com>
2006-10-07  9:53                 ` Steven Smith [this message]
2006-09-22  2:36   ` [PATCH] [XEND] Remove hard tabs Dan Smith
2006-10-12 16:33   ` Mark Williamson
2006-09-22 16:36 ` Alastair Tse

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=20061007095315.GA2111@cam.ac.uk \
    --to=sos22-xen@srcf.ucam.org \
    --cc=rmaxfiel@novell.com \
    --cc=sos22@srcf.ucam.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.