From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] How to lock-up your tap-based VM network
Date: Mon, 12 Apr 2010 21:07:18 +0100 [thread overview]
Message-ID: <201004122107.19425.paul@codesourcery.com> (raw)
In-Reply-To: <4BC34D95.7050804@siemens.com>
> A major reason for this deadlock could likely be removed by shutting
> down the tap (if peered) or dropping packets in user space (in case of
> vlan) when a NIC is stopped or otherwise shut down. Currently most (if
> not all) NIC models seem to signal both "queue full" and "RX disabled"
> via !can_receive().
No. A disabled device should return true from can_recieve, then discard the
packets in its receive callback. Failure to do so is a bug in the device. It
looks like the virtio-net device may be buggy.
Paul.
next prev parent reply other threads:[~2010-04-12 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 16:43 [Qemu-devel] How to lock-up your tap-based VM network Jan Kiszka
2010-04-12 20:07 ` Paul Brook [this message]
2010-04-12 21:49 ` Jamie Lokier
2010-04-12 23:20 ` Paul Brook
2010-04-13 12:30 ` Jan Kiszka
2010-04-13 13:02 ` Paul Brook
2010-04-13 12:22 ` Jan Kiszka
2010-04-13 12:19 ` Jan Kiszka
2010-04-13 13:03 ` Paul Brook
2010-04-13 13:15 ` Jan Kiszka
2010-04-13 18:48 ` Blue Swirl
2010-04-13 19:13 ` Blue Swirl
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=201004122107.19425.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=jan.kiszka@siemens.com \
--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).