git://ftp.safe.ca / safe / jmp / linux-2.6 / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3309daa) | patch
virtio: clarify NO_NOTIFY flag usage
authorRusty Russell <rusty@rustcorp.com.au>
Tue, 5 Feb 2008 04:49:59 +0000 (23:49 -0500)
committerRusty Russell <rusty@rustcorp.com.au>
Mon, 4 Feb 2008 12:50:00 +0000 (23:50 +1100)
commit426e3e0af5d2473e67d4256fc1340b7faebd1cc7
tree29912e63889e45307f41ef08116ecd895b17e21ctree | snapshot
parent3309daaad724dd08eb598bf9c12b7bb9daddd706commit | diff
virtio: clarify NO_NOTIFY flag usage

The other side (host) can set the NO_NOTIFY flag as an optimization,
to say "no need to kick me when you add things".  Make it clear that
this is advisory only; especially that we should always notify when
the ring is full.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Documentation/lguest/lguest.c diff | blob | history
drivers/virtio/virtio_ring.c diff | blob | history
include/linux/virtio_ring.h diff | blob | history
Full containers within linux kernel