From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Wodkowski, PawelX" <pawelx.wodkowski@intel.com>,
"Kulasek, TomaszX" <tomaszx.kulasek@intel.com>,
"yliu@fridaylinux.org" <yliu@fridaylinux.org>
Cc: "Verkamp, Daniel" <daniel.verkamp@intel.com>,
"Harris, James R" <james.r.harris@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Liu, Changpeng" <changpeng.liu@intel.com>,
"Tan, Jianfeng" <jianfeng.tan@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] vhost: add virtio configuration space messages
Date: Wed, 28 Mar 2018 11:48:01 +0200 [thread overview]
Message-ID: <3b530b7b-454b-3127-afc7-f5834c5b268e@redhat.com> (raw)
In-Reply-To: <3637fba9-b6a9-2771-995b-6f1a9c5ff927@redhat.com>
On 03/28/2018 11:33 AM, Maxime Coquelin wrote:
>
>
> On 03/28/2018 11:19 AM, Wodkowski, PawelX wrote:
>>> -----Original Message-----
>>> From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com]
>>> Sent: Wednesday, March 28, 2018 11:12 AM
>>> To: Kulasek, TomaszX <tomaszx.kulasek@intel.com>; yliu@fridaylinux.org
>>> Cc: Verkamp, Daniel <daniel.verkamp@intel.com>; Harris, James R
>>> <james.r.harris@intel.com>; Wodkowski, PawelX
>>> <pawelx.wodkowski@intel.com>; dev@dpdk.org; Liu, Changpeng
>>> <changpeng.liu@intel.com>; Tan, Jianfeng <jianfeng.tan@intel.com>
>>> Subject: Re: [dpdk-dev] [PATCH v2] vhost: add virtio configuration space
>>> messages
>>>
>>>
>>>
>>> On 03/27/2018 05:35 PM, Tomasz Kulasek wrote:
>>>> This patch adds new vhost user messages GET_CONFIG and SET_CONFIG used
>>>> for get/set virtio device's configuration space.
>>>>
>>>> Signed-off-by: Changpeng Liu <changpeng.liu@intel.com>
>>>> Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>
>>>> ---
>>>> Changes in v2:
>>>> - code cleanup
>>>>
>>>> lib/librte_vhost/rte_vhost.h | 4 ++++
>>>> lib/librte_vhost/vhost_user.c | 22 ++++++++++++++++++++++
>>>> lib/librte_vhost/vhost_user.h | 16 ++++++++++++++++
>>>> 3 files changed, 42 insertions(+)
>>>>
>>>> diff --git a/lib/librte_vhost/rte_vhost.h
>>>> b/lib/librte_vhost/rte_vhost.h
>>>> index d332069..fe30518 100644
>>>> --- a/lib/librte_vhost/rte_vhost.h
>>>> +++ b/lib/librte_vhost/rte_vhost.h
>>>> @@ -84,6 +84,10 @@ struct vhost_device_ops {
>>>> int (*new_connection)(int vid);
>>>> void (*destroy_connection)(int vid);
>>>>
>>>> + int (*get_config)(int vid, uint8_t *config, uint32_t config_len);
>>>> + int (*set_config)(int vid, uint8_t *config, uint32_t offset,
>>>> + uint32_t len, uint32_t flags);
>>>> +
>>>> void *reserved[2]; /**< Reserved for future extension */
>>>
>>> You are breaking the ABI, as you grow the size of the ops struct.
>>>
>>> Also, I'm wondering if we shouldn't have a different ops for external
>>> backends. Here these ops are more intended to the application, we could
>>> have a specific ops struct for external backends IMHO.
>>
>> What do mean by "external backends" ?
>
> Libs like SPDK or Crypto that implements their own ring processing,
> comparing to an application like DPDK that doesn't care of rings
> details.
Sorry, I meant comparing to an application like OVS*
next prev parent reply other threads:[~2018-03-28 9:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 15:17 [dpdk-dev] [PATCH] " Tomasz Kulasek
2018-03-27 15:35 ` [dpdk-dev] [PATCH v2] " Tomasz Kulasek
2018-03-28 9:11 ` Maxime Coquelin
2018-03-28 9:19 ` Wodkowski, PawelX
2018-03-28 9:33 ` Maxime Coquelin
2018-03-28 9:48 ` Maxime Coquelin [this message]
2018-03-28 9:50 ` Liu, Changpeng
2018-03-28 9:57 ` Maxime Coquelin
2018-03-28 10:03 ` Liu, Changpeng
2018-03-28 10:11 ` Maxime Coquelin
2018-03-28 10:23 ` Liu, Changpeng
2018-03-28 10:56 ` Maxime Coquelin
2018-04-19 14:39 ` Maxime Coquelin
2018-04-20 0:32 ` Liu, Changpeng
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=3b530b7b-454b-3127-afc7-f5834c5b268e@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=changpeng.liu@intel.com \
--cc=daniel.verkamp@intel.com \
--cc=dev@dpdk.org \
--cc=james.r.harris@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=pawelx.wodkowski@intel.com \
--cc=tomaszx.kulasek@intel.com \
--cc=yliu@fridaylinux.org \
/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).