From: "Michael S. Tsirkin" <mst@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Willem de Bruijn <willemb@google.com>,
netdev@vger.kernel.org, davem@davemloft.net,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH net-next v3 5/5] virtio-net: keep tx interrupts disabled unless kick
Date: Tue, 13 Apr 2021 01:06:09 -0400 [thread overview]
Message-ID: <20210413010354-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170424174930.82623-6-willemdebruijn.kernel@gmail.com>
On Mon, Apr 24, 2017 at 01:49:30PM -0400, 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 | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> index 9dd978f34c1f..003143835766 100644
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -1200,6 +1200,9 @@ static netdev_tx_t start_xmit(struct sk_buff *skb, struct net_device *dev)
> /* Free up any pending old buffers before queueing new ones. */
> free_old_xmit_skbs(sq);
>
> + if (use_napi && kick)
> + virtqueue_enable_cb_delayed(sq->vq);
> +
> /* timestamp packet in software */
> skb_tx_timestamp(skb);
I have been poking at this code today and I noticed that is
actually does enable cb where the commit log says masking interrupts.
I think the reason is that with even index previously disable cb
actually did nothing while virtqueue_enable_cb_delayed pushed
the event index out some more.
And this likely explains why it does not work well for packed,
where virtqueue_enable_cb_delayed is same as virtqueue_enable_cb.
Right? Or did I miss something?
> --
> 2.12.2.816.g2cccc81164-goog
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, jasowang@redhat.com,
virtualization@lists.linux-foundation.org, davem@davemloft.net,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next v3 5/5] virtio-net: keep tx interrupts disabled unless kick
Date: Tue, 13 Apr 2021 01:06:09 -0400 [thread overview]
Message-ID: <20210413010354-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170424174930.82623-6-willemdebruijn.kernel@gmail.com>
On Mon, Apr 24, 2017 at 01:49:30PM -0400, 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 | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> index 9dd978f34c1f..003143835766 100644
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -1200,6 +1200,9 @@ static netdev_tx_t start_xmit(struct sk_buff *skb, struct net_device *dev)
> /* Free up any pending old buffers before queueing new ones. */
> free_old_xmit_skbs(sq);
>
> + if (use_napi && kick)
> + virtqueue_enable_cb_delayed(sq->vq);
> +
> /* timestamp packet in software */
> skb_tx_timestamp(skb);
I have been poking at this code today and I noticed that is
actually does enable cb where the commit log says masking interrupts.
I think the reason is that with even index previously disable cb
actually did nothing while virtqueue_enable_cb_delayed pushed
the event index out some more.
And this likely explains why it does not work well for packed,
where virtqueue_enable_cb_delayed is same as virtqueue_enable_cb.
Right? Or did I miss something?
> --
> 2.12.2.816.g2cccc81164-goog
next prev parent reply other threads:[~2021-04-13 5:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 17:49 [PATCH net-next v3 0/5] virtio-net tx napi Willem de Bruijn
2017-04-24 17:49 ` [PATCH net-next v3 1/5] virtio-net: napi helper functions Willem de Bruijn
2017-04-24 17:49 ` Willem de Bruijn
2017-04-24 17:49 ` [PATCH net-next v3 2/5] virtio-net: transmit napi Willem de Bruijn
2017-04-24 17:49 ` Willem de Bruijn
2017-04-25 8:36 ` Jason Wang
2017-04-25 14:32 ` Willem de Bruijn
2017-04-25 8:36 ` Jason Wang
2017-04-24 17:49 ` [PATCH net-next v3 3/5] virtio-net: move free_old_xmit_skbs Willem de Bruijn
2017-04-24 17:49 ` Willem de Bruijn
2017-04-24 17:49 ` [PATCH net-next v3 4/5] virtio-net: clean tx descriptors from rx napi Willem de Bruijn
2017-04-24 17:49 ` Willem de Bruijn
2017-04-24 17:49 ` [PATCH net-next v3 5/5] virtio-net: keep tx interrupts disabled unless kick Willem de Bruijn
2017-04-24 17:49 ` Willem de Bruijn
2021-04-13 5:06 ` Michael S. Tsirkin [this message]
2021-04-13 5:06 ` Michael S. Tsirkin
2021-04-13 14:27 ` Willem de Bruijn
2021-04-13 14:27 ` Willem de Bruijn
2021-04-13 19:34 ` Michael S. Tsirkin
2021-04-13 19:34 ` Michael S. Tsirkin
2017-04-24 23:35 ` [PATCH net-next v3 0/5] virtio-net tx napi Michael S. Tsirkin
2017-04-24 23:35 ` Michael S. Tsirkin
2017-04-25 13:09 ` David Miller
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=20210413010354-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.