On Fri, Aug 15, 2014 at 11:40:08AM +0800, Jason Wang wrote:
After rx vq was enabled, we never stop polling its socket. This is sub optimal
when may lead unnecessary wake-ups after the rx net work has already been
queued. This could be optimized by stopping polling the rx net sock when
On 08/17/2014 06:20 PM, Michael S. Tsirkin wrote:
On Fri, Aug 15, 2014 at 11:40:08AM +0800, Jason Wang wrote:
After rx vq was enabled, we never stop polling its socket. This is sub
optimal
when may lead unnecessary wake-ups after the rx net work has already been
queued. This could be
After rx vq was enabled, we never stop polling its socket. This is sub optimal
when may lead unnecessary wake-ups after the rx net work has already been
queued. This could be optimized by stopping polling the rx net sock when
processing both rx and tx and restart it afterward. This could save
