[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2ae5889b-69d4-3041-d7fd-a7ea38e8c4e2@redhat.com>
Date: Thu, 20 Apr 2017 14:27:03 +0800
From: Jason Wang <jasowang@...hat.com>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>,
netdev@...r.kernel.org
Cc: mst@...hat.com, virtualization@...ts.linux-foundation.org,
davem@...emloft.net, Willem de Bruijn <willemb@...gle.com>
Subject: Re: [PATCH net-next v2 2/5] virtio-net: transmit napi
On 2017年04月19日 04:21, Willem de Bruijn wrote:
> +static void virtnet_napi_tx_enable(struct virtnet_info *vi,
> + struct virtqueue *vq,
> + struct napi_struct *napi)
> +{
> + if (!napi->weight)
> + return;
> +
> + if (!vi->affinity_hint_set) {
> + napi->weight = 0;
> + return;
> + }
> +
> + return virtnet_napi_enable(vq, napi);
> +}
> +
> static void refill_work(struct work_struct *work)
Maybe I was wrong, but according to Michael's comment it looks like he
want check affinity_hint_set just for speculative tx polling on rx napi
instead of disabling it at all.
And I'm not convinced this is really needed, driver only provide
affinity hint instead of affinity, so it's not guaranteed that tx and rx
interrupt are in the same vcpus.
Thanks
Powered by blists - more mailing lists