On 2015/12/29 6:59, Rich Lane wrote: > On Wed, Dec 23, 2015 at 11:58 PM, Tetsuya Mukawa <mukawa at igel.co.jp> wrote: >> Hi Rich and Yuanhan, >> >> I guess we have 2 implementations here. >> >> 1. rte_eth_vhost_get_queue_event() returns each event. >> 2. rte_eth_vhost_get_queue_status() returns current status of the queues. >> >> I guess option "2" is more generic manner to handle interrupts from >> device driver. >> In the case of option "1", if DPDK application doesn't call >> rte_eth_vhost_get_queue_event(), the vhost PMD needs to keep all events. >> This may exhaust memory. >> > Option 1 can be implemented in constant space by only tracking the latest > state of each > queue. I pushed a rough implementation to https://github.com/rlane/dpdk > vhost-queue-callback. > > One more example is current link status interrupt handling.
Hi Rich, I appreciate your implementation. I can understand what's your idea, and agree with it. Hi Yuanhan, What do you think his implementation? Thanks. Tetsuya
