[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121203111848.GD26167@redhat.com>
Date: Mon, 3 Dec 2012 13:18:48 +0200
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Jason Wang <jasowang@...hat.com>
Cc: Rusty Russell <rusty@...tcorp.com.au>, krkumar2@...ibm.com,
virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
bhutchings@...arflare.com, jwhan@...ewood.snu.ac.kr,
shiyer@...hat.com
Subject: Re: [net-next rfc v7 1/3] virtio-net: separate fields of
sending/receiving queue from virtnet_info
On Mon, Dec 03, 2012 at 01:15:01PM +0800, Jason Wang wrote:
> > > +
>
> > > + /* 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.
We are running from the timer, so latency is not a concern I think.
--
MST
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists