All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark McLoughlin <markmc@redhat.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] kvm:virtio-net: Run TX from the I/O thread
Date: Thu, 22 Jan 2009 12:47:02 +0000	[thread overview]
Message-ID: <1232628422.4533.14.camel@blaa> (raw)
In-Reply-To: <20090121230642.10404.65372.stgit@kvm.aw>

Hi Alex,

On Wed, 2009-01-21 at 16:08 -0700, Alex Williamson wrote:
> This is an attempt to improve the latency of virtio-net while not hurting
> throughput.  I wanted to try moving packet TX into a different thread
> so we can quickly return to the guest after it kicks us to send packets
> out.  I also switched the order of when the tx_timer comes into play, so
> we can get an inital burst of packets out, then wait for the timer to
> fire and notify us if there's more to do.  Here's what it does for me
> (average of 5 runs each, testing to a remote system on a 1Gb network):
> 
> netperf TCP_STREAM: 939.22Mb/s -> 935.24Mb/s =  99.58%
> netperf TCP_RR:      2028.72/s -> 3927.99/s  = 193.62%
> tbench:              92.99MB/s -> 99.97MB/s  = 107.51%
> 
> I'd be interested to hear if it helps or hurts anyone else.  Thanks,

Avi and I went back and forth on this one in great detail before:

  http://www.mail-archive.com/kvm@vger.kernel.org/msg06431.html

Avi's arguments make a lot of sense, but looking over those patches
again now, I still think that applying them would be a better approach
than what we have right now.

Cheers,
Mark.


  parent reply	other threads:[~2009-01-22 12:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 23:08 [PATCH] kvm:virtio-net: Run TX from the I/O thread Alex Williamson
2009-01-22 12:12 ` Avi Kivity
2009-01-22 12:48   ` Mark McLoughlin
2009-01-22 18:36     ` Alex Williamson
2009-01-22 12:47 ` Mark McLoughlin [this message]
2009-01-22 13:41   ` Avi Kivity
2009-01-22 18:43     ` Anthony Liguori
2009-01-22 13:42   ` Avi Kivity

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=1232628422.4533.14.camel@blaa \
    --to=markmc@redhat.com \
    --cc=alex.williamson@hp.com \
    --cc=kvm@vger.kernel.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 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.