Hi Tom, My two cents. Please look for [Chaks]
><snip> >Comparing the transmit path to the receive path, the guest disables >notifications after the first kick and vhost re-enables notifications >after >completing processing of the tx ring. Can a similar thing be done for >the >receive path? Once vhost sends the first notification for a received >packet >it can disable notifications and let the guest re-enable notifications >when it >has finished processing the receive ring. Also, can the virtio-net >driver do >some adaptive polling (or does napi take care of that for the guest)? > >[Chaks] A better method is to have the producer generate the kick >notifications only when the queue/ring transitions from empty to >non-empty state. The consumer is not burdened with the task of reenabling >the notifications. This of course assumes that notifications will never >get lost. If loss of notifications is a possibility, producer can keep >generating the notifications till guest signals (via some atomically >manipulated memory variable) that it started consuming. The next >notification will go out when the ring/queue again transitions from empty >to non-empty state. Chaks ============================================================ The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ============================================================ -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
