From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: chenhut03@sina.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Virtio port in virtual machine based on vmware platform could not receive tipc multicast packets.But could on openstack platform.
Date: Thu, 6 Apr 2017 15:05:11 +0800 [thread overview]
Message-ID: <20170406070511.GS18844@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <20170401085803.4372F6C01AE@webmail.sinamail.sina.com.cn>
Firstly, please do not ask question privately. Cc dev ml and remove
Thomas.
On Sat, Apr 01, 2017 at 04:58:03PM +0800, chenhut03@sina.com wrote:
> Dear Liu and Monjalon,
>
> I found that virtio port in virtual machine based on vmware platform could not
> receive tipc multicast packets. But if rte_eth_allmulticast_enable(uint8_t
> port_id) was called during virtio port driver initialization, the port could.
>
> It's strange that virtio port in virtual machine based on openstack platform
> could receive tipc multicast packets whether rte_eth_allmulticast_enable/
> rte_eth_allmulticast_disable was called or not during port driver
> initialization.
>
> So,could you please tell me:
>
> On openstack platform, why multicast packets could be received without calling
> rte_eth_allmulticast_enable during port driver initialization?
What do you mean by "on openstack platform"? What's the hypervisor? QEMU?
Is vhost-user involved?
--yliu
>
> And why multicast packets could yet be received with calling
> rte_eth_allmulticast_disable during port driver initialization?
>
>
>
> --------------------------------
>
> Best Regards,
>
> ChenDong from ZTE
>
>
parent reply other threads:[~2017-04-06 7:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20170401085803.4372F6C01AE@webmail.sinamail.sina.com.cn>]
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=20170406070511.GS18844@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=chenhut03@sina.com \
--cc=dev@dpdk.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).