From: Avi Kivity <avi@qumranet.com>
To: xming <xmingske@gmail.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: Network Overruns
Date: Sun, 14 Sep 2008 04:03:10 +0300 [thread overview]
Message-ID: <48CC62CE.6070101@qumranet.com> (raw)
In-Reply-To: <519a8b110809131600vbee71cbv6774e0d4ce2f4238@mail.gmail.com>
(re-adding list)
xming wrote:
>> What NIC model are you using in the guest?
>>
>
> I have tried 8319, e1000 and virtio both had stalls. I am using virtio
> with txqueuelen 1500 on the tap.
> I didin't had this proble with kvm 69, 70.
>
What is the oldest version that doesn't work? (i.e. when was the
regression introduced?)
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-09-14 1:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 17:29 Network Overruns Henri Cook
2008-09-13 5:09 ` Avi Kivity
2008-09-13 8:18 ` xming
2008-09-13 14:44 ` Avi Kivity
[not found] ` <519a8b110809131600vbee71cbv6774e0d4ce2f4238@mail.gmail.com>
2008-09-14 1:03 ` Avi Kivity [this message]
2008-09-14 17:56 ` xming
2008-09-23 13:09 ` xming
2008-09-23 14:27 ` xming
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=48CC62CE.6070101@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=xmingske@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