From: Jason Wang <jasowang@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
netdev@vger.kernel.org
Cc: Willem de Bruijn <willemb@google.com>,
virtualization@lists.linux-foundation.org, davem@davemloft.net,
mst@redhat.com
Subject: Re: [PATCH net-next v2 5/5] virtio-net: keep tx interrupts disabled unless kick
Date: Thu, 20 Apr 2017 14:17:21 +0800 [thread overview]
Message-ID: <72551dd3-ba91-812e-9065-d153bf8a7024@redhat.com> (raw)
In-Reply-To: <20170418202108.61920-6-willemdebruijn.kernel@gmail.com>
On 2017年04月19日 04:21, Willem de Bruijn wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> Tx napi mode increases the rate of transmit interrupts. Suppress some
> by masking interrupts while more packets are expected. The interrupts
> will be reenabled before the last packet is sent.
>
> This optimization reduces the througput drop with tx napi for
> unidirectional flows such as UDP_STREAM that do not benefit from
> cleaning tx completions in the the receive napi handler.
>
> Signed-off-by: Willem de Bruijn <willemb@google.com>
> ---
> drivers/net/virtio_net.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> index b14c82ce0032..b107ae011632 100644
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -1196,8 +1196,14 @@ static netdev_tx_t start_xmit(struct sk_buff *skb, struct net_device *dev)
> bool use_napi = sq->napi.weight;
>
> /* Free up any pending old buffers before queueing new ones. */
> - if (!use_napi)
> + if (use_napi) {
> + if (kick)
> + virtqueue_enable_cb_delayed(sq->vq);
> + else
> + virtqueue_disable_cb(sq->vq);
Since virtqueue_disable_cb() do nothing for event idx. I wonder whether
or not just calling enable_cb_dealyed() is ok here.
Btw, it does not disable interrupt at all, I propose a patch in the past
which can do more than this:
https://patchwork.kernel.org/patch/6472601/
Thanks
> + } else {
> free_old_xmit_skbs(sq);
> + }
>
> /* timestamp packet in software */
> skb_tx_timestamp(skb);
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2017-04-20 6:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170418202108.61920-1-willemdebruijn.kernel@gmail.com>
2017-04-18 20:21 ` [PATCH net-next v2 1/5] virtio-net: napi helper functions Willem de Bruijn
2017-04-18 20:21 ` [PATCH net-next v2 2/5] virtio-net: transmit napi Willem de Bruijn
2017-04-18 20:21 ` [PATCH net-next v2 3/5] virtio-net: move free_old_xmit_skbs Willem de Bruijn
2017-04-18 20:21 ` [PATCH net-next v2 4/5] virtio-net: clean tx descriptors from rx napi Willem de Bruijn
2017-04-18 20:21 ` [PATCH net-next v2 5/5] virtio-net: keep tx interrupts disabled unless kick Willem de Bruijn
[not found] ` <20170418202108.61920-6-willemdebruijn.kernel@gmail.com>
2017-04-20 6:17 ` Jason Wang [this message]
2017-04-20 14:03 ` Willem de Bruijn
[not found] ` <CAF=yD-KVwRkkGr=pGDmTTXtrrTuAuD7SmTPVtQuwu9aufoBeEQ@mail.gmail.com>
2017-04-21 23:13 ` Willem de Bruijn
[not found] ` <20170418202108.61920-3-willemdebruijn.kernel@gmail.com>
2017-04-20 6:12 ` [PATCH net-next v2 2/5] virtio-net: transmit napi Jason Wang
2017-04-20 6:27 ` Jason Wang
2017-04-20 13:58 ` Willem de Bruijn
[not found] ` <CAF=yD-K0Cwwcob+0nWXWTY_07_zwcae1GRHwdagF2pGrv8HwtA@mail.gmail.com>
2017-04-21 3:53 ` Jason Wang
2017-04-21 14:50 ` Willem de Bruijn
[not found] ` <CAF=yD-KdtvXV+=ZROcLPHJxB55wbnJOmV0MJn2AJPHugoofR0g@mail.gmail.com>
2017-04-24 16:40 ` Michael S. Tsirkin
2017-04-24 17:05 ` Willem de Bruijn
[not found] ` <CAF=yD-Lv8BptfhV+Many0iaG1Dz+LmkT2VVv5Kgo=TU31PJPHQ@mail.gmail.com>
2017-04-24 17:14 ` Michael S. Tsirkin
2017-04-24 17:51 ` Willem de Bruijn
2017-04-25 8:39 ` Jason Wang
[not found] ` <9f57a790-9157-db4d-621d-cf359c8f0718@redhat.com>
2017-04-20 16:02 ` Willem de Bruijn
[not found] ` <CAF=yD-KzHo1jVugrZKq_CmyrsqCR1zmM4Jo12OjacreKm74P8w@mail.gmail.com>
2017-04-21 18:10 ` Willem de Bruijn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=72551dd3-ba91-812e-9065-d153bf8a7024@redhat.com \
--to=jasowang@redhat.com \
--cc=davem@davemloft.net \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox