Anthony Liguori wrote:
2) cpu_physical_memory_rw due to not using preadv/pwritev?
I think both virtio-net and virtio-blk use memcpy().
With latest linux-2.6, and a development snapshot of glibc, virtio-blk
will not use memcpy() anymore but virtio-net still does on the receive
path (but not transmit).
There's still the kernel/user copy, so we have two copies on rx, one on tx.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
