[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090401170103.GU11935@one.firstfloor.org>
Date: Wed, 1 Apr 2009 19:01:03 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Gregory Haskins <ghaskins@...ell.com>
Cc: Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
agraf@...e.de, pmullaney@...ell.com, pmorreale@...ell.com,
anthony@...emonkey.ws, rusty@...tcorp.com.au,
netdev@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [RFC PATCH 00/17] virtual-bus
On Wed, Apr 01, 2009 at 10:19:49AM -0400, Gregory Haskins wrote:
> >>
> >
> > But surely you must have some specific use case in mind? Something
> > that it does better than the various methods that are available
> > today. Or rather there must be some problem you're trying
> > to solve. I'm just not sure what that problem exactly is.
> >
> Performance. We are trying to create a high performance IO infrastructure.
Ok. So the goal is to bypass user space qemu completely for better
performance. Can you please put this into the initial patch
description?
> So the administrator can then set these attributes as
> desired to manipulate the configuration of the instance of the device,
> on a per device basis.
How would the guest learn of any changes in there?
I think the interesting part would be how e.g. a vnet device
would be connected to the outside interfaces.
> So the admin would instantiate this "vdisk" device and do:
>
> 'echo /path/to/my/exported/disk.dat > /sys/vbus/devices/foo/src_path'
So it would act like a loop device? Would you reuse the loop device
or write something new?
How about VFS mount name spaces?
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
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