Thread (27 messages) flat view 27 messages, 4 authors, 2012-12-04

Re: [net-next rfc v7 1/3] virtio-net: separate fields of sending/receiving queue from virtnet_info

From: Rusty Russell <hidden>
Date: 2012-12-04 03:48:07
Also in: kvm, lkml, virtualization

Jason Wang [off-list ref] writes:
On Monday, December 03, 2012 12:25:42 PM Rusty Russell wrote:
quoted
quoted
+
+	/* Work struct for refilling if we run low on memory. */
+	struct delayed_work refill;
I can't really see the justificaiton for a refill per queue.  Just have
one work iterate all the queues if it happens, unless it happens often
(in which case, we need to look harder at this anyway).
But during this kind of iteration, we may need enable/disable the napi 
regardless of whether the receive queue has lots to be refilled. This may add 
extra latency. 
Sure, but does it actually happen?  We only use the work when we run out
of memory.  If this happens in normal behaviour we need to change
something else...

Thanks,
Rusty.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help