search for: vhost_vq_disable_vqpol

...unchanged. > + * > + * It is assumed that these functions are called relatively rarely, when vhost > + * notices that this virtqueue's usage pattern significantly changed in a way > + * that makes polling more efficient than notification, or vice versa. > + * Also, we assume that vhost_vq_disable_vqpoll() is always called on vq > + * cleanup, so any allocations done by vhost_vq_enable_vqpoll() can be > + * reclaimed. > + */ > +static void vhost_vq_enable_vqpoll(struct vhost_virtqueue *vq) > +{ > + if (vq->vqpoll.enabled) > + return; /* already enabled, nothing to do */ &g...

...unchanged. > + * > + * It is assumed that these functions are called relatively rarely, when vhost > + * notices that this virtqueue's usage pattern significantly changed in a way > + * that makes polling more efficient than notification, or vice versa. > + * Also, we assume that vhost_vq_disable_vqpoll() is always called on vq > + * cleanup, so any allocations done by vhost_vq_enable_vqpoll() can be > + * reclaimed. > + */ > +static void vhost_vq_enable_vqpoll(struct vhost_virtqueue *vq) > +{ > + if (vq->vqpoll.enabled) > + return; /* already enabled, nothing to do */ &g...

...while vqpoll.enabled is unchanged. + * + * It is assumed that these functions are called relatively rarely, when vhost + * notices that this virtqueue's usage pattern significantly changed in a way + * that makes polling more efficient than notification, or vice versa. + * Also, we assume that vhost_vq_disable_vqpoll() is always called on vq + * cleanup, so any allocations done by vhost_vq_enable_vqpoll() can be + * reclaimed. + */ +static void vhost_vq_enable_vqpoll(struct vhost_virtqueue *vq) +{ + if (vq->vqpoll.enabled) + return; /* already enabled, nothing to do */ + if (!vq->handle_kick) + return;...

...while vqpoll.enabled is unchanged. + * + * It is assumed that these functions are called relatively rarely, when vhost + * notices that this virtqueue's usage pattern significantly changed in a way + * that makes polling more efficient than notification, or vice versa. + * Also, we assume that vhost_vq_disable_vqpoll() is always called on vq + * cleanup, so any allocations done by vhost_vq_enable_vqpoll() can be + * reclaimed. + */ +static void vhost_vq_enable_vqpoll(struct vhost_virtqueue *vq) +{ + if (vq->vqpoll.enabled) + return; /* already enabled, nothing to do */ + if (!vq->handle_kick) + return;...