From: Tiwei Bie <tiwei.bie@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, changpeng.liu@intel.com, i.maximets@samsung.com,
dariusz.stojaczyk@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] vhost: add API to set protocol features flags
Date: Wed, 13 Mar 2019 13:56:33 +0800 [thread overview]
Message-ID: <20190313055633.GA8308@dpdk-tbie.sh.intel.com> (raw)
In-Reply-To: <20190312145410.570-2-maxime.coquelin@redhat.com>
On Tue, Mar 12, 2019 at 03:54:09PM +0100, Maxime Coquelin wrote:
> rte_vhost_driver_set_protocol_features API is to be used
> by external backends to advertize vhost-user protocol
> features it supports.
>
> It has to be called after rte_vhost_driver_register() and
> before rte_vhost_driver_start().
>
> Example of usage to advertize VHOST_USER_PROTOCOL_F_FOOBAR
> protocol feature:
>
> const char *path = "/tmp/vhost-user";
> uint64_t protocol_features;
> rte_vhost_driver_register(path, 0);
> rte_vhost_driver_get_protocol_features(path, &protocol_features);
> protocol_features |= VHOST_USER_PROTOCOL_F_FOOBAR;
> rte_vhost_driver_set_protocol_features(path, protocol_features);
> rte_vhost_driver_start(path);
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> Tested-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
> ---
> lib/librte_vhost/rte_vhost.h | 14 ++++++++++++++
> lib/librte_vhost/rte_vhost_version.map | 1 +
> lib/librte_vhost/socket.c | 14 ++++++++++++++
> 3 files changed, 29 insertions(+)
Reviewed-by: Tiwei Bie <tiwei.bie@intel.com>
next prev parent reply other threads:[~2019-03-13 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 14:54 [dpdk-dev] [PATCH 0/2] vhost: Support external backend only vhost-user requests Maxime Coquelin
2019-03-12 14:54 ` [dpdk-dev] [PATCH 1/2] vhost: add API to set protocol features flags Maxime Coquelin
2019-03-13 5:56 ` Tiwei Bie [this message]
2019-03-12 14:54 ` [dpdk-dev] [PATCH 2/2] vhost: support requests only handled by external backend Maxime Coquelin
2019-03-12 16:14 ` Ilya Maximets
2019-03-13 15:42 ` Maxime Coquelin
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=20190313055633.GA8308@dpdk-tbie.sh.intel.com \
--to=tiwei.bie@intel.com \
--cc=changpeng.liu@intel.com \
--cc=dariusz.stojaczyk@intel.com \
--cc=dev@dpdk.org \
--cc=i.maximets@samsung.com \
--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).