Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2211307yba; Mon, 6 May 2019 01:36:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqymnA2pdlJvdlfUZdtBHGYshwCytgtB2MVQi4Uv3OZjTNxPp4DZJk1MuHo0a0OJCaKmSJRT X-Received: by 2002:a63:6fcf:: with SMTP id k198mr30097404pgc.158.1557131804475; Mon, 06 May 2019 01:36:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557131804; cv=none; d=google.com; s=arc-20160816; b=rl9qYNziSQKQ5YEN5OEXbKqXxrFBqIk86JfvkNKWoKZBSLdzry1NVlBd6ehIboUPto NikQHlaQo5+BxmJnDQ7lS3Dm6YPYVa2iGXcD+UZzOp9f4bVs+O3ugxJxt02h1cZe5JxE Hay8jqcHhuMJKXGIuq5MrtNjvoghyUJ3EsDcWxyKgfcrsTug2ul+yoiGZHjbeQYykW8f 74P+7QbrqrcSjOQOhHhDpmsH7cfpbWPZNye/JJoKPZFcWBM4bryu7hf/66Aa2EPSXbKn OUPJ61TxEUvibmem60+5gWz8DVs1Pqz+6c1gJj4PlSoArgL25625EPKL8AU7kN+NyfoG IvGg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=5r0nN/QLahN9SrKGygZlRq5pEGdUzv3A80GQJGfoVyU=; b=G1xTo7XqaW8b88NSTQx9w85jnGys+aBI1TQDJ/LC0jDvEFjh2+U+kcB8/qhUCFW7kJ 6G2816RJFy6WRa8fjjHM0mW8yz81Dq2LQKyOgFozqeT99V72ZY/LBYoXwdJ0mrdmuzQd zZX+InSL2KmTYxsxYLGoEAmUf0VM32HqNEmYHMajGTCoQNACjxYEoGc9VYGcKrCwzTSG 402wOqPPvnSN9jXcLXqcOMiL88ahTK+4dzC5/JC9oTaPOWX4o8ndDhquLyqgf6/fPfpb j80nb2VZ0ESfM2KNrFvGH2oWJ/kX9DgGhftdnXlA0RUn3IbE+po3toxZBzOwskm2CefN ZjpQ== 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 14si14928500pfy.57.2019.05.06.01.36.29; Mon, 06 May 2019 01:36:44 -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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726287AbfEFIed (ORCPT + 99 others); Mon, 6 May 2019 04:34:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51728 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725890AbfEFIec (ORCPT ); Mon, 6 May 2019 04:34:32 -0400 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 23B3DC05B00E; Mon, 6 May 2019 08:34:32 +0000 (UTC) Received: from maximlenovopc.usersys.redhat.com (unknown [10.35.206.20]) by smtp.corp.redhat.com (Postfix) with ESMTP id B4E3119C4F; Mon, 6 May 2019 08:34:24 +0000 (UTC) Message-ID: <8ed3a93804ca136690749edcb464a60d4149a4e8.camel@redhat.com> Subject: Re: [PATCH v2 06/10] nvme/core: add mdev interfaces From: Maxim Levitsky To: Christoph Hellwig , Max Gurtovoy Cc: Fam Zheng , kvm@vger.kernel.org, Wolfram Sang , linux-nvme@lists.infradead.org, Nicolas Ferre , Keith Busch , Kirti Wankhede , Mauro Carvalho Chehab , "Paul E . McKenney" , Sagi Grimberg , Christoph Hellwig , Liang Cunming , Jens Axboe , Alex Williamson , John Ferlan , Liu Changpeng , Jens Axboe , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, Paolo Bonzini , Amnon Ilan , "David S . Miller" Date: Mon, 06 May 2019 11:34:26 +0300 In-Reply-To: <1cc7efd1852f298b01f09955f2c4bf3b20cead13.camel@redhat.com> References: <20190502114801.23116-1-mlevitsk@redhat.com> <20190502114801.23116-7-mlevitsk@redhat.com> <20190503122902.GA5081@infradead.org> <20190504064938.GA30814@lst.de> <1cc7efd1852f298b01f09955f2c4bf3b20cead13.camel@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Mon, 06 May 2019 08:34:32 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2019-05-06 at 11:31 +0300, Maxim Levitsky wrote: > On Sat, 2019-05-04 at 08:49 +0200, Christoph Hellwig wrote: > > On Fri, May 03, 2019 at 10:00:54PM +0300, Max Gurtovoy wrote: > > > Don't see a big difference of taking NVMe queue and namespace/partition > > > to > > > guest OS or to P2P since IO is issued by external entity and pooled > > > outside > > > the pci driver. > > > > We are not going to the queue aside either way.. That is where the > > last patch in this series is already working to, and which would be > > the sensible vhost model to start with. > > Why are you saying that? I actualy prefer to use a sepearate queue per > software > nvme controller, tat because of lower overhead (about half than going through > the block layer) and it better at QoS as the separate queue (or even few > queues > if needed) will give the guest a mostly guaranteed slice of the bandwidth of > the > device. Sorry for typos - I need more coffee :-) Best regards, Maxim Levitsky