From: "Loftus, Ciara" <ciara.loftus@intel.com>
To: Tetsuya Mukawa <mukawa@igel.co.jp>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ann.zhuangyanying@huawei.com" <ann.zhuangyanying@huawei.com>
Subject: Re: [dpdk-dev] [RFC PATCH] vhost: Add VHOST PMD
Date: Thu, 17 Sep 2015 13:56:13 +0000 [thread overview]
Message-ID: <74F120C019F4A64C9B78E802F6AD4CC24CB8411A@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <55F8DC9F.8030607@igel.co.jp>
>
> On 2015/09/16 1:27, Loftus, Ciara wrote:
> >> +
> >> +static int
> >> +rte_pmd_vhost_devinit(const char *name, const char *params)
> >> +{
> >> + struct rte_kvargs *kvlist = NULL;
> >> + int ret = 0;
> >> + int index;
> >> + char *iface_name;
> >> +
> >> + RTE_LOG(INFO, PMD, "Initializing pmd_vhost for %s\n", name);
> >> +
> >> + kvlist = rte_kvargs_parse(params, valid_arguments);
> >> + if (kvlist == NULL)
> >> + return -1;
> >> +
> >> + if (strlen(name) < strlen("eth_vhost"))
> >> + return -1;
> >> +
> >> + index = strtol(name + strlen("eth_vhost"), NULL, 0);
> >> + if (errno == ERANGE)
> >> + return -1;
> >> +
> >> + if (rte_kvargs_count(kvlist, ETH_VHOST_IFACE_ARG) == 1) {
> >> + ret = rte_kvargs_process(kvlist, ETH_VHOST_IFACE_ARG,
> >> + &open_iface, &iface_name);
> >> + if (ret < 0)
> >> + goto out_free;
> >> +
> >> + eth_dev_vhost_create(name, index, iface_name,
> >> rte_socket_id());
> >> + }
> >> +
> >> +out_free:
> >> + rte_kvargs_free(kvlist);
> >> + return ret;
> >> +}
> >> +
> > This suggests to me that vHost ports will only be available/created if one
> supplies the " --vdev 'eth_vhost0,iface=...' " options when launching the
> application. There seems to be no option available to add vHost ports on-the-
> fly after the init process. One would have to restart the application with
> different parameters in order to modify the vHost port configuration. Is this
> correct?
>
> Hi Ciara,
>
> Thanks for your checking and description.
> We can attach and detach a port created by vhost PMD using Port Hotplug
> functionality.
>
> example)
> ./testpmd -c f -n 4 -- -i
> testpmd> port attach eth_vhost0,iface=/tmp/aaa
>
> Does this fit your case?
>
> Thanks,
> Tetsuya
Hi,
Thanks for your reply. I wasn't aware of the hotplug functionality but this should work for this use case. Thanks!
I will continue to review the remainder of the patch and reply if I have any further feedback.
Ciara
>
> > If so, this pmd implementation will not work with Open vSwitch. OVS relies
> on the ability to call the rte_vhost_driver_register function at any point in the
> lifetime of the application, in order to create new vHost ports and
> subsequently register/create the sockets. Being bound to the selection
> chosen on the command line when launching the application is not suitable
> for OVS.
> >
> > Thanks,
> > Ciara
prev parent reply other threads:[~2015-09-17 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 3:21 [dpdk-dev] [RFC PATCH] " Tetsuya Mukawa
2015-08-28 3:21 ` [dpdk-dev] [RFC PATCH] vhost: " Tetsuya Mukawa
2015-08-28 18:18 ` Stephen Hemminger
2015-08-31 2:23 ` Tetsuya Mukawa
2015-08-31 5:14 ` Ouyang, Changchun
2015-08-31 6:29 ` Tetsuya Mukawa
2015-09-15 16:27 ` Loftus, Ciara
2015-09-16 3:06 ` Tetsuya Mukawa
2015-09-17 13:56 ` Loftus, Ciara [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=74F120C019F4A64C9B78E802F6AD4CC24CB8411A@IRSMSX106.ger.corp.intel.com \
--to=ciara.loftus@intel.com \
--cc=ann.zhuangyanying@huawei.com \
--cc=dev@dpdk.org \
--cc=mukawa@igel.co.jp \
/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).