From: Jason Wang <jasowang@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] net: Allow hubports to connect to other netdevs
Date: Tue, 16 Jan 2018 13:54:39 +0800 [thread overview]
Message-ID: <ad2d436f-aa43-f1e5-c32d-5f9e2c8887c4@redhat.com> (raw)
In-Reply-To: <28cccfd1-dca4-c074-0f74-1cf29c143a9c@redhat.com>
On 2018年01月16日 02:06, Thomas Huth wrote:
> On 15.01.2018 18:36, Thomas Huth wrote:
>> On 15.01.2018 08:40, Jason Wang wrote:
> [...]
>>> And since it was a hub, do we need to send to its netdev too inside
>>> net_hub_receive()?
>> I currently don't think so, but I'll check again...
> OK, I now think we're definitely fine here. The check is really just
> there to make sure that we do not send the packet back to the same
> sender. And I've checked with a command line like this that network
> traffic (TFTP booting in this case) works as expected:
>
> qemu-system-ppc64 -vga none -nographic \
> -netdev user,id=s1,tftp=/path/to/tftpdir,bootfile=ppc64.img \
> -netdev hubport,hubid=1,id=h1,netdev=s1 \
> -netdev hubport,hubid=1,id=h3 -device virtio-net-pci,netdev=h3 \
> -boot n -object filter-dump,id=f1,netdev=s1,file=/tmp/dump.dat
>
> Both, the behaviour of the TFTP boot in the guest and the wireshark dump
> looked fine, there were no missing packets here.
>
> Thomas
Right, I think I misread the command parameters.
Thanks
prev parent reply other threads:[~2018-01-16 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 14:32 [Qemu-devel] [PATCH] net: Allow hubports to connect to other netdevs Thomas Huth
2018-01-10 14:47 ` Paolo Bonzini
2018-01-10 15:06 ` Thomas Huth
2018-01-15 7:40 ` Jason Wang
2018-01-15 17:36 ` Thomas Huth
2018-01-15 18:06 ` Thomas Huth
2018-01-16 5:54 ` Jason Wang [this message]
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=ad2d436f-aa43-f1e5-c32d-5f9e2c8887c4@redhat.com \
--to=jasowang@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).