From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id E20017F00 for ; Fri, 13 May 2016 04:01:00 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP; 12 May 2016 19:01:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,611,1455004800"; d="scan'208";a="975277046" Received: from shwdeisgchi083.ccr.corp.intel.com (HELO [10.239.67.193]) ([10.239.67.193]) by orsmga002.jf.intel.com with ESMTP; 12 May 2016 19:00:56 -0700 To: "Michael S. Tsirkin" References: <1461892716-19122-1-git-send-email-jianfeng.tan@intel.com> <1461892716-19122-7-git-send-email-jianfeng.tan@intel.com> <20160512021208.GA17474@yliu-dev.sh.intel.com> <20160512200040-mutt-send-email-mst@redhat.com> Cc: Yuanhan Liu , dev@dpdk.org, Huawei Xie , rich.lane@bigswitch.com, nakajima.yoshihiro@lab.ntt.co.jp, p.fedin@samsung.com, ann.zhuangyanying@huawei.com, mukawa@igel.co.jp, nhorman@tuxdriver.com From: "Tan, Jianfeng" Message-ID: <16426a78-7b0d-51e7-d0ce-d1de6c7c639c@intel.com> Date: Fri, 13 May 2016 10:00:55 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20160512200040-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v4 6/8] virtio-user: add new virtual pci driver for virtio X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 02:01:01 -0000 Hi Michael, On 5/13/2016 1:02 AM, Michael S. Tsirkin wrote: > On Thu, May 12, 2016 at 03:08:05PM +0800, Tan, Jianfeng wrote: >> (2) It's more aligned to previous logic to hide the detail to differentiate >> modern/legacy device. > Why is there a need to support legacy interfaces at all? It's a container > so if it's in use one can be reasonably sure you have a new kernel. > No, there's no need. The added device, virtio-user, is parallel to legacy and modern device. But there's a feature bit inside vhost user protocol for vhost user to decide the length of header, current implementation by default set this feature bit. Thanks, Jianfeng