[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100320195359.GA11536@dtor-ws.eng.vmware.com>
Date: Sat, 20 Mar 2010 12:54:00 -0700
From: Dmitry Torokhov <dtor@...r-ws.eng.vmware.com>
To: Avi Kivity <avi@...hat.com>
Cc: Dmitry Torokhov <dtor@...are.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"pv-drivers@...are.com" <pv-drivers@...are.com>,
Alok Kataria <akataria@...are.com>,
Shaileshkumar Jain <sajain@...are.com>,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 4/4] Add VMware memory balloon driver
Hi Avi,
On Sat, Mar 20, 2010 at 06:10:57AM -0700, Avi Kivity wrote:
> On 03/19/2010 10:47 PM, Dmitry Torokhov wrote:
> > This is a virtio-based transport between VMware's hypervisor
> > and virtio_ballon driver that allows host control guest memory
> > ballooning.
> >
> >
>
> This is a little wierd since it's specific to the balloon driver. The
> virtio design is to make transport and device orthogonal so we could
> mix'n'match any driver with any transport, but this will only work with
> the balloon driver. It's also 640 lines while the original balloon
> driver is ~300. Some of that is because you're emulating a queue that
> doesn't really exist, IIUC.
Yes, this is corect. We have a dedicated balloon interface, so, while
trying to work with existing kernel infrastructure, we had to emulate
a virtual queue.
>
> So while I'd love to see other hypervisors adopt virtio, I think in this
> case it makes more sense to have your own balloon driver.
>
Fair enough. If this is a common sentiment we'll gladly prepare our
standalone driver for submission.
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists