Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp848170img; Thu, 21 Mar 2019 10:10:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqz3G5/uUcFojfolfTH7zehlB2wguuPr6IlmGDPruD15HUrjBn7LkVX6zgxGZe+4ojTKhYfF X-Received: by 2002:a62:6ec3:: with SMTP id j186mr4467531pfc.89.1553188248904; Thu, 21 Mar 2019 10:10:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553188248; cv=none; d=google.com; s=arc-20160816; b=IRDungkgCAkPfAZyn5D+CRadW6rETjz7qUqzJ9734szAwsIQzfMVHfPBYdmIUTeHA9 2mB0YOeGrcVZuKguSsQYsr/WtRiJtp+eGFY8tu+VuR7A7P75HpZOxalROIf9elGETBEF K0k8Z66FJqx6WuX054yBxOEXOgve40e7YvtqvfUsNq5mH9YcQgOk7MnH6EBolt0B82UD PNGREHGH7fdMUvD9wrS/34afywOOP/CLqQcdNri5qDWtCY0Id9zToDKn/McEmiEn3jDZ wiF8a+w9FOPL7pChrPwWJMkqjxONXNibV0rCHTCHfW2Xvt2TTygSPMiq0MDEV2qoQ/mk X5dA== 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=THkKtkO1Lr2ndI3scheNMXMyNgGWbt25GUhVu9fmk5c=; b=P6wL1026UblLLVo7lTAE8blFtnVxZS07lKmptLIv99RYrl89hwnkPa/idhBHZWrd/z fZuyFIGnUFHsoNc92AC2azbypOmNohx4HkqiUN/NdcEbEBQKgYiF+h7/ybdSYSCq+Uaj 6PqfcCNf7X2Plc0bLFo9kOKDo0ket6TONA9De32s2Mk12Gyk1hr4ZsheTleKFfOyTTfm dO6aqt6rwVeO/PCjLCN0VtTVgQFYscHhlW0WsFVcRJOuQ20xmhRJz4z0eLCoiGKc2upf GxG8jvWIY7ENgv/wBtFQeH/aKyNiIOhJ1o10O7isZo6ql0zsaW4TPerCrNeQD5TM5OYr FJ6w== 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 q19si4464823pgi.554.2019.03.21.10.10.30; Thu, 21 Mar 2019 10:10:48 -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 S1728643AbfCURIG (ORCPT + 99 others); Thu, 21 Mar 2019 13:08:06 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20224 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727958AbfCURIG (ORCPT ); Thu, 21 Mar 2019 13:08:06 -0400 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 ED1E583F3A; Thu, 21 Mar 2019 17:08:05 +0000 (UTC) Received: from maximlenovopc.usersys.redhat.com (unknown [10.35.206.30]) by smtp.corp.redhat.com (Postfix) with ESMTP id 8254F5D9C5; Thu, 21 Mar 2019 17:07:40 +0000 (UTC) Message-ID: Subject: Re: your mail From: Maxim Levitsky To: Stefan Hajnoczi Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Jens Axboe , Alex Williamson , Keith Busch , Christoph Hellwig , Sagi Grimberg , Kirti Wankhede , "David S . Miller" , Mauro Carvalho Chehab , Greg Kroah-Hartman , Wolfram Sang , Nicolas Ferre , "Paul E . McKenney" , Paolo Bonzini , Liang Cunming , Liu Changpeng , Fam Zheng , Amnon Ilan , John Ferlan Date: Thu, 21 Mar 2019 19:07:38 +0200 In-Reply-To: <20190321161352.GA21682@stefanha-x1.localdomain> References: <20190319144116.400-1-mlevitsk@redhat.com> <20190321161352.GA21682@stefanha-x1.localdomain> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 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.27]); Thu, 21 Mar 2019 17:08:06 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2019-03-21 at 16:13 +0000, Stefan Hajnoczi wrote: > On Tue, Mar 19, 2019 at 04:41:07PM +0200, Maxim Levitsky wrote: > > Date: Tue, 19 Mar 2019 14:45:45 +0200 > > Subject: [PATCH 0/9] RFC: NVME VFIO mediated device > > > > Hi everyone! > > > > In this patch series, I would like to introduce my take on the problem of > > doing > > as fast as possible virtualization of storage with emphasis on low latency. > > > > In this patch series I implemented a kernel vfio based, mediated device > > that > > allows the user to pass through a partition and/or whole namespace to a > > guest. > > > > The idea behind this driver is based on paper you can find at > > https://www.usenix.org/conference/atc18/presentation/peng, > > > > Although note that I stared the development prior to reading this paper, > > independently. > > > > In addition to that implementation is not based on code used in the paper > > as > > I wasn't being able at that time to make the source available to me. > > > > ***Key points about the implementation:*** > > > > * Polling kernel thread is used. The polling is stopped after a > > predefined timeout (1/2 sec by default). > > Support for all interrupt driven mode is planned, and it shows promising > > results. > > > > * Guest sees a standard NVME device - this allows to run guest with > > unmodified drivers, for example windows guests. > > > > * The NVMe device is shared between host and guest. > > That means that even a single namespace can be split between host > > and guest based on different partitions. > > > > * Simple configuration > > > > *** Performance *** > > > > Performance was tested on Intel DC P3700, With Xeon E5-2620 v2 > > and both latency and throughput is very similar to SPDK. > > > > Soon I will test this on a better server and nvme device and provide > > more formal performance numbers. > > > > Latency numbers: > > ~80ms - spdk with fio plugin on the host. > > ~84ms - nvme driver on the host > > ~87ms - mdev-nvme + nvme driver in the guest > > You mentioned the spdk numbers are with vhost-user-nvme. Have you > measured SPDK's vhost-user-blk? I had lot of measuments of vhost-user-blk vs vhost-user-nvme. vhost-user-nvme was always a bit faster but only a bit. Thus I don't think it makes sense to benchamrk against vhost-user-blk. Best regards, Maxim Levitsky