From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 960F7952 for ; Thu, 5 May 2016 01:14:36 +0200 (CEST) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga102.jf.intel.com with ESMTP; 04 May 2016 16:14:35 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,579,1455004800"; d="scan'208";a="97409112" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by fmsmga004.fm.intel.com with ESMTP; 04 May 2016 16:14:34 -0700 Date: Wed, 4 May 2016 16:18:19 -0700 From: Yuanhan Liu To: Jianfeng Tan Cc: David Marchand , "dev@dpdk.org" , "Xie, Huawei" Message-ID: <20160504231819.GS5641@yliu-dev.sh.intel.com> References: <1461637474-110602-1-git-send-email-jianfeng.tan@intel.com> <1461866939-38689-1-git-send-email-jianfeng.tan@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH v2] virtio: fix modify drv_flags for specific device 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: Wed, 04 May 2016 23:14:37 -0000 On Tue, May 03, 2016 at 10:05:01AM +0200, David Marchand wrote: > Hello Tan, > > On Thu, Apr 28, 2016 at 8:08 PM, Jianfeng Tan wrote: > > Issue: virtio's drv_flags are decided by devices types (modern vs legacy), > > and which kernel driver is used, and the negotiated features (especially > > VIRTIO_NET_STATUS) with backend, which makes it possible to multiple > > virtio devices have different versions of drv_flags, but this variable > > is currently shared by each virtio device. > > The wording is a bit strange, maybe the sentence is a bit too long. Agreed. Besides that, it just described the fact that we are sharing one flag for all virtio devices, but it didn't state what's wrong with it, and what's the per-device flag for. From this point of view, I don't think you are actually solving an "issue", as I don't see one from your description. > But the rest looks good to me. > > Acked-by: David Marchand Thanks for the review. --yliu