public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
To: Eric Van Hensbergen <ericvh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	v9fs-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	lguest-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Lguest] [RFC] 9p Virtualization Transports
Date: Sun, 02 Sep 2007 07:14:57 +1000	[thread overview]
Message-ID: <1188681297.10802.38.camel@localhost.localdomain> (raw)
In-Reply-To: <11883271601857-git-send-email-ericvh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Tue, 2007-08-28 at 13:52 -0500, Eric Van Hensbergen wrote:
> The lguest and kvm transports are functional, but we are still working out
> remaining bugs and need to spend some time focusing on performance issues.
> I wanted to send out this "preview" patch set to the community to solicit
> ideas on things we can do differently/better.

Hi Eric,

	Patches look reasonable, but just a heads-up: lguest will be moving to
virtio, as will kvm.  That means a single implementation for both
(yay!), but it does complicate your life in the short term 8(

	Dor has published a kvm virtio implementation, and we've already
discussed a couple of modifications.  I expect that to be nailed in the
next 2 weeks tho, and lguest will follow.

Thanks!
Rusty.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-09-01 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11883271601857-git-send-email-ericvh@gmail.com>
     [not found] ` <11883271601227-git-send-email-ericvh@gmail.com>
     [not found]   ` <11883271602233-git-send-email-ericvh@gmail.com>
     [not found]     ` <11883271602233-git-send-email-ericvh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-29 16:29       ` [RFC] 9p: add KVM/QEMU pci transport Anthony Liguori
2007-08-29 16:37         ` [V9fs-developer] " Latchesar Ionkov
     [not found]           ` <f158dc670708290937p73188b2aq12903c6f1c65a276-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-30  4:40             ` [Lguest] [V9fs-developer] [RFC] 9p: add KVM/QEMUpci transport Dor Laor
     [not found] ` <11883271601857-git-send-email-ericvh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-08-31 20:22   ` [RFC] 9p Virtualization Transports Andi Kleen
2007-09-01 21:14   ` Rusty Russell [this message]
     [not found]     ` <1188681297.10802.38.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-09-03 20:19       ` [Lguest] " Eric Van Hensbergen

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=1188681297.10802.38.camel@localhost.localdomain \
    --to=rusty-8n+1lvoiyb80n/f98k4iww@public.gmane.org \
    --cc=ericvh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=lguest-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=v9fs-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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