I was going through the documentation and I had found that avail_event is used to set the threshold value after which notification will be sent. If the kick is required or not will be decide on the basis of the following condition every time: (u16)(new_idx - avail_event - 1) < (u16)(new_idx - old_idx) Right now due to avail_event value the kick is been made for every start_xmit call, I wanted to know, how could I modify the avail_event value . So that the kicks are not made for each start_xmit() call. Regards Nitesh Narayan Lal On Tue, May 14, 2013 at 1:23 PM, Michael S. Tsirkin <mst@xxxxxxxxxx> wrote: > On Tue, May 14, 2013 at 11:37:35AM +0530, nitesh narayan lal wrote: >> I was wondering how exactly vq->event is been set and used? >> Regards >> Nitesh Narayan Lal >> >> >> On Tue, May 14, 2013 at 11:37 AM, nitesh narayan lal >> <niteshnarayanlalleo@xxxxxxxxx> wrote: >> > Hi Michael, >> > I had seen the virtqueue_kick_prepare() where vring_need_event() is >> > been used, but somehow for every start_xmit() call vq->event and >> > need_kick is been set to true. >> > Due to which for every start_xmit() its kicking via notify() routine. >> > Regards >> > Nitesh Narayan Lal > > > vq->event if set when guest and host agree to use event index. > needs_kick comes from comparison of event index (element for > which host requested an event) and avail index. > > We trigger the event when we make available the element > for which host requested notification. > > More detail in the virtio spec. > > -- > MST _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
