From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Wenfeng Liu <liuwf@arraynetworks.com.cn>
Cc: jianfeng.tan@intel.com, maxime.coquelin@redhat.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/virtio-user: support changing tap interface name
Date: Tue, 28 Mar 2017 14:21:40 +0800 [thread overview]
Message-ID: <20170328062140.GY18844@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1490702949-5944-1-git-send-email-liuwf@arraynetworks.com.cn>
On Tue, Mar 28, 2017 at 12:09:09PM +0000, Wenfeng Liu wrote:
> This patch adds a new option 'iface' to change the interface name of
> tap device with vhost-kernel as backend.
>
> Signed-off-by: Wenfeng Liu <liuwf@arraynetworks.com.cn>
> Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
This option applies only to vhost-kernel backend, you may need do a
sanity check and raise an exception if it's given for vhost-user
backend.
--yliu
next prev parent reply other threads:[~2017-03-28 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 12:09 Wenfeng Liu
2017-03-28 6:21 ` Yuanhan Liu [this message]
2017-03-28 6:59 ` [dpdk-dev] 答复: " Wenfeng Liu
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=20170328062140.GY18844@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=liuwf@arraynetworks.com.cn \
--cc=maxime.coquelin@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).