lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 18 May 2010 12:27:19 +0200 From: Jes Sorensen <Jes.Sorensen@...hat.com> To: "Michael S. Tsirkin" <mst@...hat.com> CC: Rusty Russell <rusty@...tcorp.com.au>, Jiri Pirko <jpirko@...hat.com>, Shirley Ma <xma@...ibm.com>, Amit Shah <amit.shah@...hat.com>, Mark McLoughlin <markmc@...hat.com>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, quintela@...hat.com, alex.williamson@...hat.com Subject: Re: [PATCH] virtio: put last seen used index into ring itself On 05/18/10 02:47, Michael S. Tsirkin wrote: > Generally, the Host end of the virtio ring doesn't need to see where > Guest is up to in consuming the ring. However, to completely understand > what's going on from the outside, this information must be exposed. > For example, host can reduce the number of interrupts by detecting > that the guest is currently handling previous buffers. > > Fortunately, we have room to expand: the ring is always a whole number > of pages and there's hundreds of bytes of padding after the avail ring > and the used ring, whatever the number of descriptors (which must be a > power of 2). Hi Michael, Small build fix for this against Linus upstream. Jes Fix build of virtio_net.c Signed-off-by: Jes.Sorensen@...hat.com --- diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c index d37e5be..679e2df 100644 --- a/drivers/net/virtio_net.c +++ b/drivers/net/virtio_net.c @@ -23,6 +23,7 @@ #include <linux/module.h> #include <linux/virtio.h> #include <linux/virtio_net.h> +#include <linux/virtio_ring.h> #include <linux/scatterlist.h> #include <linux/if_vlan.h> #include <linux/slab.h> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists