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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 38CAFC4167B for ; Thu, 7 Dec 2023 15:19:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1443429AbjLGPTQ (ORCPT ); Thu, 7 Dec 2023 10:19:16 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52854 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232946AbjLGPTO (ORCPT ); Thu, 7 Dec 2023 10:19:14 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B5D3719A; Thu, 7 Dec 2023 07:19:20 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 46A52227A87; Thu, 7 Dec 2023 16:19:17 +0100 (CET) Date: Thu, 7 Dec 2023 16:19:17 +0100 From: Christoph Hellwig To: Paolo Bonzini Cc: Stefan Hajnoczi , Li Feng , Jens Axboe , "Michael S. Tsirkin" , Jason Wang , Xuan Zhuo , "open list:BLOCK LAYER" , open list , "open list:VIRTIO BLOCK AND SCSI DRIVERS" , Christoph Hellwig Subject: Re: [PATCH] virtio_blk: set the default scheduler to none Message-ID: <20231207151917.GA20401@lst.de> References: <20231207043118.118158-1-fengli@smartx.com> <20231207145159.GB2147383@fedora> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 07, 2023 at 03:55:17PM +0100, Paolo Bonzini wrote: > > This seems similar to commit f8b12e513b95 ("virtio_blk: revert > > QUEUE_FLAG_VIRT addition") where changing the default sounded good in > > theory but exposed existing users to performance regressions. [...] > > I don't want to be overly conservative. The virtio_blk driver has > > undergone changes in this regard from the legacy block layer to blk-mq > > (without an I/O scheduler) to blk-mq (mq-deadline). > > IIRC there were also regressions in both virtio-blk and virtio-scsi > when switching from the legacy block layer to blk-mq. So perhaps I > *am* a bit more conservative, but based on past experience, this patch > seems not to be a great idea for practical use cases. Agreed. I'm in fact not exactly happy about the rather odd BLK_MQ_F_NO_SCHED_BY_DEFAULT flag to start with.