From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Liu, Yong" <yong.liu@intel.com>, "Bie, Tiwei" <tiwei.bie@intel.com>
Cc: "Wang, Zhihong" <zhihong.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/virtio-user: add unsupported features mask
Date: Wed, 27 Jun 2018 08:47:42 +0200 [thread overview]
Message-ID: <6f409b78-f889-e3fb-2f63-d91940674dfc@redhat.com> (raw)
In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E630CA896@SHSMSX103.ccr.corp.intel.com>
On 06/26/2018 11:02 AM, Liu, Yong wrote:
>
>
>> -----Original Message-----
>> From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com]
>> Sent: Tuesday, June 26, 2018 4:08 PM
>> To: Liu, Yong <yong.liu@intel.com>; Bie, Tiwei <tiwei.bie@intel.com>
>> Cc: Wang, Zhihong <zhihong.wang@intel.com>; dev@dpdk.org
>> Subject: Re: [PATCH] net/virtio-user: add unsupported features mask
>>
>>
>>
>> On 06/25/2018 03:10 PM, Marvin Liu wrote:
>>> This patch introduces unsupported features mask for virtio-user device.
>>> For virtio-user server mode, when reconnecting virtio-user will
>>> retrieve vhost devcie features as base and then unmask unsupported
>> s/devcie/device/
>>> features.
>>
>> I am not sure to understand why you are doing it like this.
>>
>> Shouldn't you just:
>> 1. Don't advertise features you don't want to support
>> 2. In server mode, save the negotiated features, and re-use it when
>> reconnect happens?
>>
> Maxime,
> I think our vhost reconnect design is following qemu vhost-user server mode. Virtio-user will try to support connected vhost device.
> So device_features of virtio user just retrieve from vhost device.
> And in server mode, we have recorded previous feature bits and used it for later negotiation. But virtio user device_features which may has changed by vdev parameters. This mask will guaranty device_features correct.
Ok, get it now, thanks for the clarification.
Please reword the variable name as I proposed, and pick this patch
directly in your in_order series.
With name change, feel free to add:
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
Maxime
> Thanks,
> Marvin
>
>> Also, I find "unmask" a bit misleading, why not something like "unsupp"
>> or "unsupported"?
>>
>> Thanks,
>> Maxime
prev parent reply other threads:[~2018-06-27 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 13:10 Marvin Liu
2018-06-26 8:08 ` Maxime Coquelin
2018-06-26 9:02 ` Liu, Yong
2018-06-27 6:47 ` 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=6f409b78-f889-e3fb-2f63-d91940674dfc@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=yong.liu@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).