From: Rusty Russell <rusty@rustcorp.com.au>
To: netdev@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org
Subject: [RFC] virtio: orphan skbs if we're relying on timer to free them
Date: Mon, 18 May 2009 22:18:47 +0930 [thread overview]
Message-ID: <200905182218.47975.rusty@rustcorp.com.au> (raw)
We check for finished xmit skbs on every xmit, or on a timer (unless
the host promises to force an interrupt when the xmit ring is empty).
This can penalize userspace tasks which fill their sockbuf. Not much
difference with TSO, but measurable with large numbers of packets.
There are a finite number of packets which can be in the transmission
queue. We could fire the timer more than every 100ms, but that would
just hurt performance for a corner case. This seems neatest.
With interrupt when Tx ring empty:
Seconds TxPkts TxIRQs
1G TCP Guest->Host: 3.76 32833 32758
1M normal pings: 111 1000008 997463
1M 1k pings (-l 120): 55 1000007 488920
Without interrupt, without orphaning:
1G TCP Guest->Host: 3.64 32806 1
1M normal pings: 106 1000008 1
1M 1k pings (-l 120): 68 1000005 1
With orphaning:
1G TCP Guest->Host: 3.86 32821 1
1M normal pings: 102 1000007 1
1M 1k pings (-l 120): 43 1000005 1
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
---
drivers/net/virtio_net.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
--- a/drivers/net/virtio_net.c
+++ b/drivers/net/virtio_net.c
@@ -522,6 +522,11 @@ static int start_xmit(struct sk_buff *sk
{
struct virtnet_info *vi = netdev_priv(dev);
+ /* We queue a limited number; don't let that delay writers if
+ * we are slow in getting tx interrupt. */
+ if (!vi->free_in_tasklet)
+ skb_orphan(skb);
+
again:
/* Free up any pending old buffers before queueing new ones. */
free_old_xmit_skbs(vi);
next reply other threads:[~2009-05-18 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 12:48 Rusty Russell [this message]
2009-05-19 2:40 ` [RFC] virtio: orphan skbs if we're relying on timer to free them David Miller
2009-05-21 6:57 ` Rusty Russell
2009-05-21 7:15 ` David Miller
2009-05-21 17:24 ` Dimitris Michailidis
2009-05-25 11:01 ` Rusty Russell
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=200905182218.47975.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).