Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp2072717ybn; Thu, 26 Sep 2019 06:39:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqz3kWmLsHiLKXdGapoldia6yjWeRwAlKZz1mOAcbkemqinHNKkzQ0hWwYWCLTtKWZPhf+X0 X-Received: by 2002:a50:c3c7:: with SMTP id i7mr3726309edf.138.1569505186255; Thu, 26 Sep 2019 06:39:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569505186; cv=none; d=google.com; s=arc-20160816; b=uBq7Dhnwm3nIU/QYlrhteNWUgVzqLzF9AIe+GjtA5HEWBKWJDT4ZKvdKQEAv+CzuX4 xeUhkrR8HQSN+8zjZGWkGd1Wr9GYlMdFSWs+0115hqtgAyJ9qKqsW0OXXo/7tlzU1CPg v45nsujx4FWTVtQzXrBHPDVetMRKTxsZTyrGbScj5bTaAxe27kJKUOlZ+H7ZhOtHAWT9 QB+04TwNdQH8nYxZYKICGWLII1prfviaeMtqXa/d7URrMEwCdVDd6rCLow33MzLniyX8 kdM0y2pZ5s3qE+lyQkIN3ywQkSmGDYNf8vxGjOMwO271jsWVnqBDC+aWHRZtibGFDvFs Br3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=3YhV9bTM58l1NfJ26TH0dKSFGmn70IacsqlK4m9+oI4=; b=YVnyB2xjy6+qXX+2UOxN3MV01cGB+8L69o7pIkf9BWwkFA24FOyT7oBZTDtP1g1k9O zkgQe95VSlbvC40pFiFm3fWZy9AY8zGh8+/Uf1APA69WQXZtryNZedRlH+MFFJzgQxkd GHzXwPVvtQ+w0/awxletuQsr4Bu8kSlMHJdJ9TtWw7ac8bi/ShtCyYLjQ4d2E1AP3e5D 0zvN83wfP2xqJivnQAfk3+MK7WrxjGNicnRuLSVUvUsZbbaGMNgOkIWepPEXS27ZzelU YhV8eyFuvNGV3bfZOrjOT/2/kCCyKGZGA4HpHNKKwNq0KpTGnnoqmWYB0QBd0/d0kGi/ kgKA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f2si1090021ejq.395.2019.09.26.06.39.18; Thu, 26 Sep 2019 06:39:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726969AbfIZNhO (ORCPT + 99 others); Thu, 26 Sep 2019 09:37:14 -0400 Received: from mga17.intel.com ([192.55.52.151]:27835 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726094AbfIZNhO (ORCPT ); Thu, 26 Sep 2019 09:37:14 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Sep 2019 06:37:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,552,1559545200"; d="scan'208";a="364730259" Received: from dpdk-virtio-tbie-2.sh.intel.com (HELO ___) ([10.67.104.73]) by orsmga005.jf.intel.com with ESMTP; 26 Sep 2019 06:37:11 -0700 Date: Thu, 26 Sep 2019 21:34:23 +0800 From: Tiwei Bie To: "Michael S. Tsirkin" Cc: jasowang@redhat.com, alex.williamson@redhat.com, maxime.coquelin@redhat.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, dan.daly@intel.com, cunming.liang@intel.com, zhihong.wang@intel.com, lingshan.zhu@intel.com Subject: Re: [PATCH] vhost: introduce mdev based hardware backend Message-ID: <20190926133423.GA15574@___> References: <20190926045427.4973-1-tiwei.bie@intel.com> <20190926042156-mutt-send-email-mst@kernel.org> <20190926131439.GA11652@___> <20190926091945-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190926091945-mutt-send-email-mst@kernel.org> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 26, 2019 at 09:26:22AM -0400, Michael S. Tsirkin wrote: > On Thu, Sep 26, 2019 at 09:14:39PM +0800, Tiwei Bie wrote: > > > 4. Does device need to limit max ring size? > > > 5. Does device need to limit max number of queues? > > > > I think so. It's helpful to have ioctls to report the max > > ring size and max number of queues. > > Also, let's not repeat the vhost net mistakes, let's lock > everything to the order required by the virtio spec, > checking status bits at each step. > E.g.: > set backend features > set features > detect and program vqs > enable vqs > enable driver > > and check status at each step to force the correct order. > e.g. don't allow enabling vqs after driver ok, etc Got it. Thanks a lot! Regards, Tiwei > > -- > MST