Messages in this thread | | | Date | Wed, 1 Apr 2009 19:01:03 +0200 | From | Andi Kleen <> | 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@linux.intel.com -- Speaking for myself only.
| |