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 5207EC43219 for ; Thu, 29 Sep 2022 11:36:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235343AbiI2Lgi (ORCPT ); Thu, 29 Sep 2022 07:36:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57262 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235320AbiI2Lge (ORCPT ); Thu, 29 Sep 2022 07:36:34 -0400 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7356013D1DB; Thu, 29 Sep 2022 04:36:33 -0700 (PDT) Received: from cwcc.thunk.org (pool-173-48-120-46.bstnma.fios.verizon.net [173.48.120.46]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 28TBaKDZ022953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 29 Sep 2022 07:36:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1664451381; bh=AdtewCAf9XNJr9bFIHpIke2+G5PbSnpa1S/HqBIX9dY=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=MSPsXOzbnuaTlYMxq6au6RnbGj7vyCrUzNWhPRl7UaDJbkmhinbvonmwZoNdtcTUX PNC7Unuh3UBRGua3NbASM7Ag6Vqs5eusq2t0wrTC6oHl8KGFo7taZ4OZffO7fcDKs8 woKTkrLcFdxdr+dfo1ISBXvvobw1PyMIHLMV87/U8eSXRVCJMmPmEt3n/xgPyqSd4x NDaEAKUZjF+zTA68VKIlSxs553pxfhDev9kii6GUVpkuUqZZoWwL+kxSVgM1zai+SZ z7oHo+WcnaTl2ma490gox3//1spNnhqEN21Yor0zdIgQIgVytx8vEZTh1XADKVRdSi Wms027zlnVb2w== Received: by cwcc.thunk.org (Postfix, from userid 15806) id 0BD3715C00C9; Thu, 29 Sep 2022 07:36:20 -0400 (EDT) Date: Thu, 29 Sep 2022 07:36:20 -0400 From: "Theodore Ts'o" To: Thorsten Leemhuis Cc: "linux-ext4@vger.kernel.org" , "regressions@lists.linux.dev" , "stable@vger.kernel.org" Subject: Re: significant drop fio IOPS performance on v5.10 #forregzbot Message-ID: References: <357ace228adf4e859df5e9f3f4f18b49@amazon.com> <1cdc68e6a98d4e93a95be5d887bcc75d@amazon.com> <5c819c9d6190452f9b10bb78a72cb47f@amazon.com> <9e3a4bf9-c909-d6aa-28c8-5fbbea9f5ae3@leemhuis.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9e3a4bf9-c909-d6aa-28c8-5fbbea9f5ae3@leemhuis.info> Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org This is a repeat of a discussion regarding changing the default of dioread_nolock. Note that you can "revert" this change in defaults by using the mount options "nodioread_nolock" (or "dioread_lock"). There were some good reasons why the change in the default was made, though. #regzbot invalid: caused by a change of defaults that (among others) was done for security reasons, see Ted's answer in https://lore.kernel.org/all/Yypx6VQRbl3bFP2v@mit.edu/ for details - Ted