From 30ea341c68cd56b387d2a0013979412f0ca1c855 Mon Sep 17 00:00:00 2001 From: rusty Date: Thu, 7 Nov 2013 03:51:21 +0000 Subject: 2.2.2.1: remove advice on notification for empty buffers. A driver can notify whenever it wants, but it should only make a difference to buggy devices. As per meeting 2013-11-05: http://markmail.org/message/3cjjeakzkfzcqk5c Signed-off-by: Rusty Russell git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@88 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652 --- virtio-v1.0-wd01-part1-specification.txt | 9 --------- 1 file changed, 9 deletions(-) diff --git a/virtio-v1.0-wd01-part1-specification.txt b/virtio-v1.0-wd01-part1-specification.txt index 5db34df..22aaed5 100644 --- a/virtio-v1.0-wd01-part1-specification.txt +++ b/virtio-v1.0-wd01-part1-specification.txt @@ -602,10 +602,6 @@ operates as follows: 1. Place the buffer(s) into free descriptor(s). - (a) If there are no free descriptors, the guest may choose to - notify the device even if notifications are suppressed (to - reduce latency).[8] - 2. Place the id of the buffer in the next ring entry of the available ring. @@ -4067,11 +4063,6 @@ separate cache lines. [7] These fields are kept here because this is the only part of the virtqueue written by the device -[8] The Linux drivers do this only for read-only buffers: for -write-only buffers, it is assumed that the driver is merely -trying to keep the receive buffer ring full, and no notification -of this expected condition is necessary. - [9] https://lists.linux-foundation.org/mailman/listinfo/virtualization [11] Even if it does mean documenting design or implementation -- cgit v1.2.3