From: Rongqing Li <rongqing.li@windriver.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 2/2] hub: change hub can_receive() strategy
Date: Fri, 24 Aug 2012 16:33:42 +0800 [thread overview]
Message-ID: <50373C66.9080303@windriver.com> (raw)
In-Reply-To: <50373955.8020504@redhat.com>
On 2012年08月24日 16:20, Paolo Bonzini wrote:
> A link-down NIC should always return 1 from can_receive (and will drop
> the packet). Is that the real bug here?
>
A link-down NIC always return 0 from can_receive.
Yes, it is a bug.
-Roy
> Paolo
>
>
--
Best Reagrds,
Roy | RongQing Li
next prev parent reply other threads:[~2012-08-24 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 7:56 [Qemu-devel] [PATCH 1/2] Usb: create the receive queue for the virtual USB NIC rongqing.li
2012-08-24 7:56 ` [Qemu-devel] [PATCH 2/2] hub: change hub can_receive() strategy rongqing.li
2012-08-24 8:20 ` Paolo Bonzini
2012-08-24 8:33 ` Rongqing Li [this message]
2012-08-24 10:11 ` Stefan Hajnoczi
2012-08-24 12:25 ` [Qemu-devel] [PATCH 1/2] Usb: create the receive queue for the virtual USB NIC Stefan Hajnoczi
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=50373C66.9080303@windriver.com \
--to=rongqing.li@windriver.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).