All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Fischer, Anna" <anna.fischer@hp.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Network I/O performance
Date: Tue, 19 May 2009 07:53:52 +0300	[thread overview]
Message-ID: <4A123B60.9090901@redhat.com> (raw)
In-Reply-To: <20090519013027.GB8566@gondor.apana.org.au>

Herbert Xu wrote:
>> Yes, there's a known issue with UDP, where we don't report congestion  
>> and the queues start dropping packets.  There's a patch for tun queued  
>> for the next merge window; you'll need a 2.6.31 host for that IIRC  
>> (Herbert?)
>>     
>
> It should be in 2.6.30 in fact.  However, this is for outbound
> traffic only since inbound traffic shouldn't have this problem
> of the guest sending faster than the wire.
>   

Is there a corresponding qemu change?  Or is this a already handled by 
the existing code?

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2009-05-19  4:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  0:28 Network I/O performance Fischer, Anna
2009-05-13  7:23 ` Avi Kivity
2009-05-13 15:56   ` Fischer, Anna
2009-05-17 21:14     ` Avi Kivity
2009-05-19  1:30       ` Herbert Xu
2009-05-19  4:53         ` Avi Kivity [this message]
2009-05-19  7:18       ` tun/tap and Vlans (was: Re: Network I/O performance) Lukas Kolbe
2009-05-19  7:45         ` tun/tap and Vlans Avi Kivity
2009-05-19 19:46           ` Lukas Kolbe
2009-05-20 10:25           ` Fischer, Anna
2009-05-20 10:38             ` Avi Kivity
2009-05-19 21:22       ` Does KVM suffer from ACK-compression as you increase the number of VMs? Andrew de Andrade
2009-05-20 10:15       ` Network I/O performance Fischer, Anna

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=4A123B60.9090901@redhat.com \
    --to=avi@redhat.com \
    --cc=anna.fischer@hp.com \
    --cc=herbert@gondor.apana.org.au \
    --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.