search for: virtq_used_f_no_notify

Displaying 4 results from an estimated 4 matches for "virtq_used_f_no_notify".

kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
2018 Dec 13
2
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
...y depend on the notification from the guest? Quoting the text from http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html /* The device uses this in used->flags to advise the driver: don?t kick me * when you add a buffer. It?s unreliable, so it?s simply an * optimization. */ #define VIRTQ_USED_F_NO_NOTIFY 1 I interpret that the notification is simply an optimization, not a reliable notification mechanism. So the kernel vhost should not bet the farm on it. We encounter the same race condition in kernel vhost?s RX traffic direction which causes the kernel vhost to be stuck due to missed interrupt/n...
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
2018 Dec 13
2
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
...y depend on the notification from the guest? Quoting the text from http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html /* The device uses this in used->flags to advise the driver: don?t kick me * when you add a buffer. It?s unreliable, so it?s simply an * optimization. */ #define VIRTQ_USED_F_NO_NOTIFY 1 I interpret that the notification is simply an optimization, not a reliable notification mechanism. So the kernel vhost should not bet the farm on it. We encounter the same race condition in kernel vhost?s RX traffic direction which causes the kernel vhost to be stuck due to missed interrupt/n...
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
2018 Dec 17
1
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
...ttp://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html > > > > /* The device uses this in used->flags to advise the driver: don?t kick me > * when you add a buffer. It?s unreliable, so it?s simply an > * optimization. */ > #define VIRTQ_USED_F_NO_NOTIFY 1 > > > > I interpret that the notification is simply an optimization, not a reliable > notification mechanism. What was meant I think is that suppression is unreliable. >So the kernel vhost should not bet the farm on it. >...
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
2018 Dec 17
0
kernel vhost demands an interrupt from guest when the ring is full in order to enable guest to submit new packets to the queue
...om > > > > http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html > > > > /* The device uses this in used->flags to advise the driver: don?t kick me > * when you add a buffer. It?s unreliable, so it?s simply an > * optimization. */ > #define VIRTQ_USED_F_NO_NOTIFY 1 > > > > I interpret that the notification is simply an optimization, not a reliable > notification mechanism. What was meant I think is that suppression is unreliable. >So the kernel vhost should not bet the farm on it. > > > > We encounter the same race...