Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command

[RFC PATCH 0/4] virtio-net: don't busy poll for cvq command · Jason Wang <jasowang@redhat.com> · 2022-12-22
[RFC PATCH 1/4] virtio-net: convert rx mode setting to use workqueue · Jason Wang <jasowang@redhat.com> · 2022-12-22
[RFC PATCH 2/4] virtio_ring: switch to use BAD_RING() · Jason Wang <jasowang@redhat.com> · 2022-12-22
[RFC PATCH 3/4] virtio_ring: introduce a per virtqueue waitqueue · Jason Wang <jasowang@redhat.com> · 2022-12-22
[RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Jason Wang <jasowang@redhat.com> · 2022-12-22
Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Alvaro Karsz <alvaro.karsz@solid-run.com> · 2022-12-22
Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Jason Wang <jasowang@redhat.com> · 2022-12-22
Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Alvaro Karsz <alvaro.karsz@solid-run.com> · 2022-12-22
Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Jason Wang <jasowang@redhat.com> · 2022-12-23
Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Alvaro Karsz <alvaro.karsz@solid-run.com> · 2022-12-23
Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Jason Wang <jasowang@redhat.com> · 2022-12-26
Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Eugenio Perez Martin <eperezma@redhat.com> · 2022-12-22
Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Jason Wang <jasowang@redhat.com> · 2022-12-23
Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Eugenio Perez Martin <eperezma@redhat.com> · 2022-12-23
Re: [RFC PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq command · Jason Wang <jasowang@redhat.com> · 2022-12-26

From: Alvaro Karsz <alvaro.karsz@solid-run.com>
Date: 2022-12-22 15:55:52
Also in: lkml, virtualization

My point is that the device may complete the control command after the timeout,
so, if I'm not mistaken, next time we send a control command and call
virtqueue_wait_for_used we'll get the previous response.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help