From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Rusty Russell" <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, kvm-devel@lists.sourceforge.net,
v9fs-developer@lists.sourceforge.net, lguest@ozlabs.org
Subject: Re: [Lguest] [RFC] 9p Virtualization Transports
Date: Mon, 3 Sep 2007 15:19:54 -0500 [thread overview]
Message-ID: <a4e6962a0709031319r63a91829v14de2ec17ac37711@mail.gmail.com> (raw)
In-Reply-To: <1188681297.10802.38.camel@localhost.localdomain>
On 9/1/07, Rusty Russell <rusty@rustcorp.com.au> wrote:
> 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.
>
> 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.
>
yeah, I've been emailing Dor -- it sounds like he'll have stuff ready
for the 2.6.24 merge window -- that being the case, I'll write a
virtio transport and mothball the PCI and lguest transports. They
were straightforward to write (a couple hours for the lguest
transport) and the lguest transport was a good learning experience --
so I'm not shedding tears over wasted effort.
-eric
prev parent reply other threads:[~2007-09-03 20:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 18:52 Eric Van Hensbergen
2007-08-28 18:52 ` [RFC] 9p: Make transports dynamic Eric Van Hensbergen
2007-08-28 18:52 ` [RFC] 9p: add KVM/QEMU pci transport Eric Van Hensbergen
2007-08-28 18:52 ` [RFC] 9p: add lguest transport Eric Van Hensbergen
2007-08-28 18:52 ` [REFERENCE ONLY] 9p: add shared memory transport Eric Van Hensbergen
2007-08-28 19:33 ` [RFC] 9p: add KVM/QEMU pci transport Christoph Hellwig
2007-08-28 20:08 ` [kvm-devel] " Arnd Bergmann
2007-08-28 20:41 ` Latchesar Ionkov
2007-08-28 23:59 ` [Lguest] " Dor Laor
2007-08-28 20:56 ` Eric Van Hensbergen
2007-08-29 0:01 ` Dor Laor
2007-08-29 16:29 ` Anthony Liguori
2007-08-29 16:37 ` [V9fs-developer] " Latchesar Ionkov
2007-08-30 4:40 ` [Lguest] [V9fs-developer] [kvm-devel] [RFC] 9p: add KVM/QEMUpci transport Dor Laor
2007-08-31 20:22 ` [kvm-devel] [RFC] 9p Virtualization Transports Andi Kleen
2007-09-01 21:14 ` [Lguest] " Rusty Russell
2007-09-03 20:19 ` 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=a4e6962a0709031319r63a91829v14de2ec17ac37711@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=v9fs-developer@lists.sourceforge.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
all inboxes | Powered by JetHome®