Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2840021rwd; Fri, 26 May 2023 12:03:58 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6v0tEM9SvHeb5rffHWahTXgOYM5i6BC3bvRfLbrFXlB/qqofZJCCfZpuCWMeMfg2ywYLGO X-Received: by 2002:a05:6a20:9185:b0:101:2923:56cd with SMTP id v5-20020a056a20918500b00101292356cdmr267247pzd.62.1685127838289; Fri, 26 May 2023 12:03:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685127838; cv=none; d=google.com; s=arc-20160816; b=pPFcB8txEdmIXgTSt/OW4+xAzF0eTjyyruvl0c9fCdGNWrFUpjsFudUhI97UhJ2zph 0Sr2u6NXEL96plNdP2tiX1BxgHS34H7LoA9HCWtfwHOVVK4Okm9Fkr/QSLVoOvwHD0rp Ng05XiRz/kyKbvLYoDrZYZ2ofhLbxvxWfczu+JYg9fStHCkpj3IPNMUykx33ytHrs8R1 qw9IAY8a3dIFoipitzbWsMZWDAu13gxzR206cBNXHgSH7A+9fvCFFLEwYOD5OQvUhrsl 9ienrOwJTLRIM/+WTUkKDk7zAO2nPYjE/SeP4R/qR8dNq/I3xP/nZeDIpGGjtNesv9fM 5/gA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=SC3QuxZifneOZBhZF54TVMUnSROnxAUB8mJntY3DYLA=; b=gKQuVEaGoD0aiKZAPIgfq3YCMHNJKjht9ZWW6ruL+xXJXqq4JFMWXY+kC1fPt6T+/E n2x0nC+4kDo/RYQM5jbxl64bUddAghBHbwaNLHJwtKyQJiCwS6IKIbkb8G774vJ8Z3Vt UeZXXsNDGb1LS+RnzHL1qnpyHX8nvRqiL0+szORdoOi7LCtVsX2hl5mdVuI0nGBQ8rZP /9ft0ceUpI5ezzBDXwDMhF75t1hJYHVY3z7Nurcu7zAzI940US5jvvWiJkBYb6BNSUxs TinBPQN7opGkuetFFwqUIsR1OuQi5zvfoXu/KoRcCHh1HhBaBhp5mA2Hu3fRTuK80eFl vfwA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b=aGq+uwJc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z22-20020a637e16000000b005347fcb785dsi1119249pgc.181.2023.05.26.12.03.42; Fri, 26 May 2023 12:03:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b=aGq+uwJc; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237674AbjEZSoE (ORCPT + 99 others); Fri, 26 May 2023 14:44:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53252 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229882AbjEZSoC (ORCPT ); Fri, 26 May 2023 14:44:02 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 46A82E65; Fri, 26 May 2023 11:43:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=SC3QuxZifneOZBhZF54TVMUnSROnxAUB8mJntY3DYLA=; b=aGq+uwJcZ2GwzvoAOVaDo+A/5e 4GfeZUw+m2279aQn4gfFuyfOanPcGaDB2nTSnB+zXJHXDjAK7YI3gweGfiHmXDd3kURuJHwaBvyTZ R3zA+BIbA0SfXRSMeHsQampNLfBRkGpC1vL/1X0Vf3NeArkee+nlNFhUOsW1dTxCDWOFGdaJQn3Iz OTaqRm5wt/Cp8hULL+gEjXn7uFjzC4f/qlmApbPYMtL3WcCurdXgptPbigQP/dfVT+UPvnLEXbfPx l91JLrC4FpfZ+D6WZ3n6LuK9/qr04EVvVg0Q5u4TPM+sYaRV72Y7NQs0Qm4LF7/4qzZiv5fajb+ZV MHEmsflw==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1q2cPP-0032TG-0U; Fri, 26 May 2023 18:43:27 +0000 Date: Fri, 26 May 2023 19:43:26 +0100 From: Matthew Wilcox To: Luis Chamberlain Cc: hughd@google.com, akpm@linux-foundation.org, brauner@kernel.org, djwong@kernel.org, p.raghav@samsung.com, da.gomez@samsung.com, rohan.puri@samsung.com, rpuri.linux@gmail.com, a.manzanares@samsung.com, dave@stgolabs.net, yosryahmed@google.com, keescook@chromium.org, hare@suse.de, kbusch@kernel.org, patches@lists.linux.dev, linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [RFC v2 0/8] add support for blocksize > PAGE_SIZE Message-ID: References: <20230526075552.363524-1-mcgrof@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 26, 2023 at 10:33:53AM -0700, Luis Chamberlain wrote: > On Fri, May 26, 2023 at 02:54:12PM +0100, Matthew Wilcox wrote: > > You're coming at this from a block layer perspective, and we have two > > ways of doing large block devices -- qemu nvme and brd. tmpfs should > > be like other filesystems and opportunistically use folios of whatever > > size makes sense. > > I figured the backing block size would be a good reason to use high > order folios for filesystems, and this mimicks that through the super > block block size. Although usage of the block size would be moved to > the block device and tmpfs use an page order, what other alternatives > were you thinking? Use the readahead code like other filesystems to determine what size of folios to allocate. Also use the size of writes to determine what size of folio to allocate, as in this patchset: https://lore.kernel.org/linux-fsdevel/20230520163603.1794256-1-willy@infradead.org/