From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6BFC5C04A6B for ; Mon, 6 May 2019 12:59:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3987F206BF for ; Mon, 6 May 2019 12:59:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726294AbfEFM72 (ORCPT ); Mon, 6 May 2019 08:59:28 -0400 Received: from verein.lst.de ([213.95.11.211]:52212 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725856AbfEFM71 (ORCPT ); Mon, 6 May 2019 08:59:27 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id 36EC567358; Mon, 6 May 2019 14:59:09 +0200 (CEST) Date: Mon, 6 May 2019 14:59:09 +0200 From: Christoph Hellwig To: Maxim Levitsky Cc: Christoph Hellwig , Max Gurtovoy , Fam Zheng , kvm@vger.kernel.org, Wolfram Sang , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, 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 , Nicolas Ferre , Paolo Bonzini , Amnon Ilan , "David S . Miller" Subject: Re: [PATCH v2 06/10] nvme/core: add mdev interfaces Message-ID: <20190506125909.GB5288@lst.de> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1cc7efd1852f298b01f09955f2c4bf3b20cead13.camel@redhat.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 06, 2019 at 11:31:27AM +0300, Maxim Levitsky wrote: > 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. The downside is that your create tons of crap code in the core nvme driver for your specific use case that no one cares about. Which is why it is completely unacceptable. If you want things to go fast make the block layer go fast, don't add your very special bypass.