On Tue, 2007-07-17 at 06:31 -0700, Dor Laor wrote:
Hi Rusty,
I was curious if there are any implementations of your virtio
substrate for KVM yet? And if not, I can offer help to get this
done
as
I have an immediate need for a ring-buffer like PV channel.
Regards,
-Greg
Actually I was
Rusty Russell wrote:
You mean backend? For networking it makes a great deal of sense. For
block it makes far less sense (COW, weird formats, etc).
For block you probably want both: userspace driver which can handle all
sorts of funny image files, and a kernel driver doing a 1:1 mapping to a
Rusty Russell wrote:
On Tue, 2007-07-17 at 23:49 -0700, Dor Laor wrote:
On Tue, 2007-07-17 at 06:31 -0700, Dor Laor wrote:
btw: Rusty - what do you think of virtio for the host?
You mean backend? For networking it makes a great deal of sense. For
block it makes far
On Wednesday 18 July 2007, Gerd Hoffmann wrote:
Rusty Russell wrote:
You mean backend? For networking it makes a great deal of sense. For
block it makes far less sense (COW, weird formats, etc).
For block you probably want both: userspace driver which can handle all
sorts of funny
Arnd Bergmann wrote:
On Wednesday 18 July 2007, Gerd Hoffmann wrote:
Rusty Russell wrote:
You mean backend? For networking it makes a great deal of sense. For
block it makes far less sense (COW, weird formats, etc).
For block you probably want both: userspace driver which
On Thursday 19 July 2007, Anthony Liguori wrote:
Interestingly, once you have the kernel driver that maps a block device,
you can do most of the useful user scenarios by means of /dev/loop
and/or device mapper.
Not quite. Using device mapper to implement something like qcow turns
out
Arnd Bergmann wrote:
On Thursday 19 July 2007, Anthony Liguori wrote:
Interestingly, once you have the kernel driver that maps a block device,
you can do most of the useful user scenarios by means of /dev/loop
and/or device mapper.
Not quite. Using device mapper to implement
Arnd Bergmann wrote:
On Thursday 19 July 2007, Anthony Liguori wrote:
Interestingly, once you have the kernel driver that maps a block device,
you can do most of the useful user scenarios by means of /dev/loop
and/or device mapper.
Not quite. Using device mapper to implement
Hi Rusty,
I was curious if there are any implementations of your virtio
substrate for KVM yet? And if not, I can offer help to get this done as
I have an immediate need for a ring-buffer like PV channel.
Regards,
-Greg
-
Hi Rusty,
I was curious if there are any implementations of your virtio
substrate for KVM yet? And if not, I can offer help to get this done
as
I have an immediate need for a ring-buffer like PV channel.
Regards,
-Greg
Actually I was planning of doing it. I'm maintaining our not-merged PV
On Tue, 2007-07-17 at 06:31 -0700, Dor Laor wrote:
You're welcome to rip my ring code ;)
Point me at the code, if you would. I would be happy to use it as a
base. :)
-
This SF.net email is sponsored by DB2 Express
You're welcome to rip my ring code ;)
Point me at the code, if you would. I would be happy to use it as a
base. :)
It's under git://kvm.qumranet.com/home/dor/export/[kvm.git
kvm-userspace.git]
Enojy, I hope that in a week or two (busy) I'll start sending patches
with cleanup of the
current
12 matches
Mail list logo