From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Lieven <lieven-lists@dlhnet.de>
Cc: oliver.francke@filoo.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] rtl8139: flush queued packets when RxBufPtr is written
Date: Mon, 27 May 2013 10:32:25 +0200 [thread overview]
Message-ID: <20130527083225.GA21969@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <51A2FA0E.4090906@dlhnet.de>
On Mon, May 27, 2013 at 08:15:42AM +0200, Peter Lieven wrote:
> I ocassionally have seen a probably related problem in the past. It mainly happend with rtl8139 under
> WinXP where we most likely use rtl8139 due to lack of shipped e1000 drivers.
>
> My question is if you see increasing dropped packets on the tap device if this problem occurs?
>
> tap36 Link encap:Ethernet HWaddr b2:84:23:c0:e2:c0
> inet6 addr: fe80::b084:23ff:fec0:e2c0/64 Scope:Link
> UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
> RX packets:5816096 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3878744 errors:0 dropped:13775 overruns:0 carrier:0
> collisions:0 txqueuelen:500
> RX bytes:5161769434 (5.1 GB) TX bytes:380415916 (380.4 MB)
My reading of the tun code is that will see TX dropped increase. This
is because tun keeps a finite size queue of tx packets. Since QEMU
userspace is not monitoring the tap fd anymore we'll never drain the
queue and soon enough the TX dropped counter will begin incrementing.
> In my case as well the only option to recover without shutting down the whole vServer is Live Migration
> to another Node.
>
> However, I also see this problem under qemu-kvm-1.2.0 while Oliver reported it does not happen there.
Yes, the patch that exposes this problem was only merged in 1.2.1.
Can you still reproduce the problem now that the patch has been merged
into qemu.git/master?
Stefan
next prev parent reply other threads:[~2013-05-27 8:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 12:50 [Qemu-devel] [PATCH] rtl8139: flush queued packets when RxBufPtr is written Stefan Hajnoczi
2013-05-22 12:53 ` Andreas Färber
2013-05-22 13:33 ` Stefan Hajnoczi
2013-05-24 14:34 ` Stefan Hajnoczi
2013-05-27 6:15 ` Peter Lieven
2013-05-27 8:32 ` Stefan Hajnoczi [this message]
2013-05-27 10:19 ` Peter Lieven
2013-05-27 14:07 ` Oliver Francke
2013-05-27 14:24 ` Peter Lieven
2013-05-27 15:29 ` Stefan Hajnoczi
2013-05-28 6:27 ` Peter Lieven
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=20130527083225.GA21969@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=lieven-lists@dlhnet.de \
--cc=oliver.francke@filoo.de \
--cc=qemu-devel@nongnu.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).