similar to: [PATCH v3] Add virtio-scsi to the virtio spec

Hi all, here is the specification for a virtio-based SCSI host (controller, HBA, you name it). The virtio SCSI host is the basis of an alternative storage stack for KVM. This stack would overcome several limitations of the current solution, virtio-blk: 1) scalability limitations: virtio-blk-over-PCI puts a strong upper limit on the number of devices that can be added to a guest. Common

Hi all, here is the specification for a virtio-based SCSI host (controller, HBA, you name it). The virtio SCSI host is the basis of an alternative storage stack for KVM. This stack would overcome several limitations of the current solution, virtio-blk: 1) scalability limitations: virtio-blk-over-PCI puts a strong upper limit on the number of devices that can be added to a guest. Common

Hi all, here is the specification for a virtio-based SCSI host (controller, HBA, you name it). The virtio SCSI host is the basis of an alternative storage stack for KVM. This stack would overcome several limitations of the current solution, virtio-blk: 1) scalability limitations: virtio-blk-over-PCI puts a strong upper limit on the number of devices that can be added to a guest. Common

Hi all, here is the specification for a virtio-based SCSI host (controller, HBA, you name it). The virtio SCSI host is the basis of an alternative storage stack for KVM. This stack would overcome several limitations of the current solution, virtio-blk: 1) scalability limitations: virtio-blk-over-PCI puts a strong upper limit on the number of devices that can be added to a guest. Common

The original idea of the VIRTIO_BALLOON_F_MUST_TELL_HOST feature was to let drivers skip usage of the deflate queue when leaking the balloon ("silent deflation"). Guests may benefit from silent deflate by aggressively inflating the balloon; they know that they will be able to use ballooned pages without issuing a (blocking) request to the device. The previous patch redefined the

Add an rpmsg appendix to the virtio spec and tag it as Appendix H. Push the SCSI host appendix to 'I' so the appendices order stays according to the virtio device ids. Patch is against: http://ozlabs.org/~rusty/virtio-spec/virtio-0.9.4.lyx Tested with LyX 2.0.0. Signed-off-by: Ohad Ben-Cohen <ohad at wizery.com> Cc: Rusty Russell <rusty at rustcorp.com.au> Cc:

Add an rpmsg appendix to the virtio spec and tag it as Appendix H. Push the SCSI host appendix to 'I' so the appendices order stays according to the virtio device ids. Patch is against: http://ozlabs.org/~rusty/virtio-spec/virtio-0.9.4.lyx Tested with LyX 2.0.0. Signed-off-by: Ohad Ben-Cohen <ohad at wizery.com> Cc: Rusty Russell <rusty at rustcorp.com.au> Cc:

The idea of the VIRTIO_BALLOON_F_MUST_TELL_HOST feature is to let drivers skip usage of the deflate queue when leaking the balloon ("silent deflation"). Guests may benefit from silent deflate by aggressively inflating the balloon; they know that they will be able to use ballooned pages without issuing a (blocking) request to the device. The problem is that this feature is a

The idea of the VIRTIO_BALLOON_F_MUST_TELL_HOST feature is to let drivers skip usage of the deflate queue when leaking the balloon ("silent deflation"). Guests may benefit from silent deflate by aggressively inflating the balloon; they know that they will be able to use ballooned pages without issuing a (blocking) request to the device. The problem is that this feature is a

I'm working on a patchset (to follow shortly) that modified the notificatin hand-off in virtio to be basically like Xen: each side published an index, the other side only triggers an event when it crosses that index value (Xen event indexes start at 1, ours start at 0 for backward-compatiblity, but that's minor). Especially for testing, it is very convenient to have separate feature bits

I'm working on a patchset (to follow shortly) that modified the notificatin hand-off in virtio to be basically like Xen: each side published an index, the other side only triggers an event when it crosses that index value (Xen event indexes start at 1, ours start at 0 for backward-compatiblity, but that's minor). Especially for testing, it is very convenient to have separate feature bits

Add an option to modify the notificatin hand-off in virtio to be basically like Xen: each side published an index, the other side only triggers an event when it crosses that index value (Xen event indexes start at 1, ours start at 0 for backward-compatiblity, but that's minor). Since we've run out of bits in the 32 bit field, I added another 32 bit and bit 31 enables that. I started with

Add an option to modify the notificatin hand-off in virtio to be basically like Xen: each side published an index, the other side only triggers an event when it crosses that index value (Xen event indexes start at 1, ours start at 0 for backward-compatiblity, but that's minor). Since we've run out of bits in the 32 bit field, I added another 32 bit and bit 31 enables that. I started with

The diff below is an update to virtio-spec with specification of a stats vq added to virtio-blk. The idea behind adding a stats vq is to simplify pull of information which exists only on the guest and can't be collected on the host. The idea is basically same as the stats vq which exists in virtio-balloon and reporting host memory statistics. --- diff --git a/old/virtio-spec.lyx

The diff below is an update to virtio-spec with specification of a stats vq added to virtio-blk. The idea behind adding a stats vq is to simplify pull of information which exists only on the guest and can't be collected on the host. The idea is basically same as the stats vq which exists in virtio-balloon and reporting host memory statistics. --- diff --git a/old/virtio-spec.lyx

On Tue, May 28, 2013 at 07:40:18PM +0200, Paolo Bonzini wrote: > The original idea of the VIRTIO_BALLOON_F_MUST_TELL_HOST feature was to > let drivers skip usage of the deflate queue when leaking the balloon > ("silent deflation"). Guests may benefit from silent deflate by > aggressively inflating the balloon; they know that they will be able to > use ballooned pages

Each virtio scsi HBA has global request queue limits. But the passthrough LUNs (scsi-generic) come from different host HBAs may have different request queue limits. If the guest sends commands that exceed the host limits, the commands will be rejected by host HAB. To address this issue, this patch adds a per-LUN parameter query via the control queue, and defines some parameter query types. The

Each virtio scsi HBA has global request queue limits. But the passthrough LUNs (scsi-generic) come from different host HBAs may have different request queue limits. If the guest sends commands that exceed the host limits, the commands will be rejected by host HAB. To address this issue, this patch adds a per-LUN parameter query via the control queue, and defines some parameter query types. The

Add multiqueue support to virtio network device. Add a new feature flag VIRTIO_NET_F_MULTIQUEUE for this feature, a new configuration field max_virtqueue_pairs to detect supported number of virtqueues as well as a new command VIRTIO_NET_CTRL_STEERING to program packet steering. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> -- Changes from v2: Address Jason's comments on v2: -

Add multiqueue support to virtio network device. Add a new feature flag VIRTIO_NET_F_MULTIQUEUE for this feature, a new configuration field max_virtqueue_pairs to detect supported number of virtqueues as well as a new command VIRTIO_NET_CTRL_STEERING to program packet steering. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> -- Changes from v2: Address Jason's comments on v2: -