From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Ilya Maximets <i.maximets@samsung.com>,
dev@dpdk.org, changpeng.liu@intel.com, tiwei.bie@intel.com,
dariusz.stojaczyk@intel.com
Subject: Re: [dpdk-dev] [PATCH 2/2] vhost: support requests only handled by external backend
Date: Wed, 13 Mar 2019 16:42:40 +0100 [thread overview]
Message-ID: <8fc721a3-b37d-a5fa-db1f-32e14453ce61@redhat.com> (raw)
In-Reply-To: <a7050e8b-8ecf-8d26-644d-9e3688214ce7@samsung.com>
On 3/12/19 5:14 PM, Ilya Maximets wrote:
> On 12.03.2019 17:54, Maxime Coquelin wrote:
>> External backends may have specific requests to handle, and so
>> we don't want the vhost-user lib to handle these requests as
>> errors.
>>
>> This patch also changes the experimental API by introducing
>> RTE_VHOST_MSG_RESULT_NOT_HANDLED so that vhost-user lib
>> can report an error if a message is handled neither by
>> the vhost-user library nor by the external backend.
>>
>> The logic changes a bit so that if the callback returns
>> with ERR, OK or REPLY, it is considered the message
>> is handled by the external backend so it won't be
>> handled by the vhost-user library.
>> It is still possible for an external backend to listen
>> to requests that have to be handled by the vhost-user
>> library like SET_MEM_TABLE, but the callback have to
>> return NOT_HANDLED in that case.
>>
>> Vhost-crypto backend is ialso adapted to this API change.
>>
>> Suggested-by: Ilya Maximets <i.maximets@samsung.com>
>> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>> Tested-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
>> ---
>> lib/librte_vhost/rte_vhost.h | 16 +++++--
>> lib/librte_vhost/vhost_crypto.c | 10 +++-
>> lib/librte_vhost/vhost_user.c | 82 +++++++++++++++++++++------------
>> 3 files changed, 71 insertions(+), 37 deletions(-)
>>
>> diff --git a/lib/librte_vhost/rte_vhost.h b/lib/librte_vhost/rte_vhost.h
>> index c9c392975..b1c5a0908 100644
>> --- a/lib/librte_vhost/rte_vhost.h
>> +++ b/lib/librte_vhost/rte_vhost.h
>> @@ -121,6 +121,8 @@ enum rte_vhost_msg_result {
>> RTE_VHOST_MSG_RESULT_OK = 0,
>> /* Message handling successful and reply prepared */
>> RTE_VHOST_MSG_RESULT_REPLY = 1,
>> + /* Message not handled */
>> + RTE_VHOST_MSG_RESULT_NOT_HANDLED,
>> };
>>
>> /**
>> @@ -135,11 +137,13 @@ enum rte_vhost_msg_result {
>> * If the handler requires skipping the master message handling, this variable
>> * shall be written 1, otherwise 0.
>
> Above statement should be updated because 'skip_master' removed.
Right.
> BTW, maybe it's better to squash these two typedef's as they are
> equal now? Comment parts that differs could be moved to the definition
> of the 'struct rte_vhost_user_extern_ops'.
Good idea, doing it now.
>> * @return
>> - * VH_RESULT_OK on success, VH_RESULT_REPLY on success with reply,
>> - * VH_RESULT_ERR on failure
>> + * RTE_VHOST_MSG_RESULT_OK on success,
>> + * RTE_VHOST_MSG_RESULT_REPLY on success with reply,
>> + * RTE_VHOST_MSG_RESULT_ERR on failure,
>> + * RTE_VHOST_MSG_RESULT_NOT_HANDLED if message was not handled.
>> */
>> typedef enum rte_vhost_msg_result (*rte_vhost_msg_pre_handle)(int vid,
>> - void *msg, uint32_t *skip_master);
>> + void *msg);
>>
Thanks,
Maxime
prev parent reply other threads:[~2019-03-13 15:42 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
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 [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=8fc721a3-b37d-a5fa-db1f-32e14453ce61@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=changpeng.liu@intel.com \
--cc=dariusz.stojaczyk@intel.com \
--cc=dev@dpdk.org \
--cc=i.maximets@samsung.com \
--cc=tiwei.bie@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).