From: "Liu, Changpeng" <changpeng.liu@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
Ilya Maximets <i.maximets@samsung.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Stojaczyk, Dariusz" <dariusz.stojaczyk@intel.com>,
"Bie, Tiwei" <tiwei.bie@intel.com>,
"Wang, Zhihong" <zhihong.wang@intel.com>,
Jason Wang <jasowang@redhat.com>,
"Stojaczyk, Dariusz" <dariusz.stojaczyk@intel.com>
Subject: Re: [dpdk-dev] vhost: add virtio configuration space access socket messages
Date: Thu, 28 Feb 2019 12:49:59 +0000 [thread overview]
Message-ID: <FF7FC980937D6342B9D289F5F3C7C2625B7C60A1@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <05528ce3-ee7d-1f31-35a9-8938436f260f@redhat.com>
> -----Original Message-----
> From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com]
> Sent: Wednesday, February 27, 2019 6:05 PM
> To: Liu, Changpeng <changpeng.liu@intel.com>; Ilya Maximets
> <i.maximets@samsung.com>; dev@dpdk.org
> Cc: Stojaczyk, Dariusz <dariusz.stojaczyk@intel.com>; Bie, Tiwei
> <tiwei.bie@intel.com>; Wang, Zhihong <zhihong.wang@intel.com>; Jason Wang
> <jasowang@redhat.com>
> Subject: Re: vhost: add virtio configuration space access socket messages
>
>
>
> On 2/27/19 10:50 AM, Liu, Changpeng wrote:
> >> What we need to do is fix vhost lib so that you don't have anything to
> >> do in dpdk to add support for the new requests.
> >>
> >> So we need to fix the few bits in vhost_user_msg_handler() I mentionned
> >> yesterday. And I also notice we are missing
> >> rte_vhost_driver_set_protocol_feature(), so that you can advertise
> >> VHOST_USER_PROTOCOL_F_CONFIG support by your external backend.
> > Sounds good to me, I will not post a new version and wait for the new API.
>
> I just posted the RFC, could you try it and let us know if it works for
> you?
Yeah, it can work for us.
>
> Thanks,
> Maxime
>
> >> I'll try to cook the dpdk patch today.
> >>
> >> Cheers,
next prev parent reply other threads:[~2019-02-28 12:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 7:51 [dpdk-dev] [PATCH] " Changpeng Liu
2019-02-25 7:48 ` Jason Wang
2019-02-25 11:49 ` Stojaczyk, Dariusz
2019-02-25 12:05 ` Stojaczyk, Dariusz
[not found] ` <CGME20190225132001eucas1p25c1e925b895b3ab36da0aca27110e15c@eucas1p2.samsung.com>
2019-02-25 13:19 ` [dpdk-dev] " Ilya Maximets
2019-02-26 7:01 ` Liu, Changpeng
2019-02-26 7:39 ` Ilya Maximets
2019-02-26 8:13 ` Liu, Changpeng
2019-02-26 8:42 ` Ilya Maximets
2019-02-26 12:32 ` Maxime Coquelin
2019-02-26 13:36 ` Ilya Maximets
2019-02-26 13:43 ` Maxime Coquelin
2019-02-26 14:07 ` Ilya Maximets
2019-02-27 9:04 ` Maxime Coquelin
2019-02-27 11:48 ` Ilya Maximets
2019-02-27 1:31 ` Liu, Changpeng
2019-02-27 9:12 ` Maxime Coquelin
2019-02-27 9:50 ` Liu, Changpeng
2019-02-27 10:04 ` Maxime Coquelin
2019-02-28 12:49 ` Liu, Changpeng [this message]
2019-02-27 1:41 ` Tiwei Bie
[not found] ` <CGME20190225135328eucas1p1560252488ef0f0db87f0509d2bb7813c@eucas1p1.samsung.com>
2019-02-25 13:53 ` Ilya Maximets
2019-02-26 7:02 ` 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=FF7FC980937D6342B9D289F5F3C7C2625B7C60A1@SHSMSX103.ccr.corp.intel.com \
--to=changpeng.liu@intel.com \
--cc=dariusz.stojaczyk@intel.com \
--cc=dev@dpdk.org \
--cc=i.maximets@samsung.com \
--cc=jasowang@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=zhihong.wang@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).