Rusty Russell wrote:
Networking hardware generally services descriptors in a FIFO manner.
Well, ethernet guarantees order. Not sure about others tho...
OT: Does that hold for bonded interfaces too?
virtio may not (for example, it may offload copies of larger packets to
a
On Mon, 2007-06-04 at 14:25 +0300, Avi Kivity wrote:
Rusty Russell wrote:
Networking hardware generally services descriptors in a FIFO manner.
Well, ethernet guarantees order. Not sure about others tho...
OT: Does that hold for bonded interfaces too?
Sorry, I don't know.
On Mon, Jun 04, 2007 at 02:25:32PM +0300, Avi Kivity wrote:
OT: Does that hold for bonded interfaces too?
Yes. By default traffic to the same destination MAC always stick to
one interface. You could select a layer3+4 hashing policy but even
that guarantees a single flow will stick to one
Rusty Russell wrote:
This attempts to implement a virtual I/O layer which should allow
common drivers to be efficiently used across most virtual I/O
mechanisms. It will no-doubt need further enhancement.
The details of probing the device are left to hypervisor-specific
code: it simple
On Sat, 2007-06-02 at 09:30 +0300, Avi Kivity wrote:
Rusty Russell wrote:
+ * virtio_ops - virtio abstraction layer
+ * @add_outbuf: prepare to send data to the other end:
+ * vdev: the virtio_device
+ * sg: the description of the buffer(s).
+ * num: the size of the sg array.
+ *
This attempts to implement a virtual I/O layer which should allow
common drivers to be efficiently used across most virtual I/O
mechanisms. It will no-doubt need further enhancement.
The details of probing the device are left to hypervisor-specific
code: it simple constructs the struct
