From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 067461B62E for ; Tue, 30 Jan 2018 15:59:36 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 449B75B30F; Tue, 30 Jan 2018 14:59:35 +0000 (UTC) Received: from [10.36.112.22] (ovpn-112-22.ams2.redhat.com [10.36.112.22]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6FF515DC1E; Tue, 30 Jan 2018 14:59:32 +0000 (UTC) To: Zhihong Wang , dev@dpdk.org Cc: jianfeng.tan@intel.com, tiwei.bie@intel.com, yliu@fridaylinux.org, cunming.liang@intel.com, xiao.w.wang@intel.com, dan.daly@intel.com References: <1514000203-69699-1-git-send-email-zhihong.wang@intel.com> <1514000203-69699-2-git-send-email-zhihong.wang@intel.com> From: Maxime Coquelin Message-ID: <67d70715-2e0a-6623-df06-b65f800ebb42@redhat.com> Date: Tue, 30 Jan 2018 15:59:30 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <1514000203-69699-2-git-send-email-zhihong.wang@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Tue, 30 Jan 2018 14:59:35 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH RFC 1/2] vhost: make capabilities configurable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 14:59:36 -0000 Hi Zhihong On 12/23/2017 04:36 AM, Zhihong Wang wrote: > This patch makes vhost device capabilities configurable to adopt various > engines. Such capabilities include supported features, protocol features, > queue number. APIs are introduced to let app configure these capabilities. Why does the vDPA driver need to mask protocol features? Maxime