From: ? ? <heringlinux@outlook.com>
To: dev <dev@dpdk.org>
Cc: yuanhan.liu <yuanhan.liu@linux.intel.com>,
huawei.xie <huawei.xie@intel.com>
Subject: [dpdk-dev] The virtio device mac is empty in vhostuser type.
Date: Thu, 9 Nov 2017 03:24:14 +0000 [thread overview]
Message-ID: <BM1PR01MB0131D6C15C2F803653D0AE13A5570@BM1PR01MB0131.INDPRD01.PROD.OUTLOOK.COM> (raw)
Hi,
When I attached a virtio device to ovs bridge in vhostuser type, the virtual port does not have the mac address.
After checked the dpdk code, I found the 'mac' which is the member of struct 'virtio_net' is empty.
It only been assigned in case VHOST_USER_SEND_RARP of function 'vhost_user_msg_handler'.
But the comments said VHOST_USER_SEND_RARP would be handled during VM migration.
Therefore I would like to ask when I launch the dpdk vhost-user program, how could I get the virtio NIC MAC address?
Thanks
________________________________
Best Regards,
Hering
heringlinux@outlook.com
next reply other threads:[~2017-11-09 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 3:24 ? ? [this message]
2017-11-10 5:44 ` Tan, Jianfeng
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=BM1PR01MB0131D6C15C2F803653D0AE13A5570@BM1PR01MB0131.INDPRD01.PROD.OUTLOOK.COM \
--to=heringlinux@outlook.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
--cc=yuanhan.liu@linux.intel.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).