Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp970096rwr; Thu, 20 Apr 2023 08:22:15 -0700 (PDT) X-Google-Smtp-Source: AKy350ZipEnTQxxjhiKr0hPua2+Z7d/cejMK7qS1W6Y0dOxDIGyDGYQLrMn5x3M5DuKWPIJaZt8e X-Received: by 2002:a17:90a:3947:b0:249:88a2:fb60 with SMTP id n7-20020a17090a394700b0024988a2fb60mr2034988pjf.31.1682004135117; Thu, 20 Apr 2023 08:22:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1682004135; cv=none; d=google.com; s=arc-20160816; b=G3fr1VMkGmWT/Qf0P6ZQ93zk9FeFTjsL6QB2G9HKEw+Zv2gIW9qchlKM+Mnus/OJ1m ekLcSbL4eMbA29odTcTKSe5bSjimKSbaiG+7AcAsQWQyXxpU1Cgng/GMPev0Rx84JGIR SD7yl074D1EVZX8cdYhnWzLr+uSiIDikOyvzj8HhYwwVToXXp1FX0fu/D6k87MbEHWMj V+qJiui+8FtySQAC1mWfitlVKrFu98N2Ak2L7pm3RmIgUhDwMJjDkCXnZTJX4340d2AW jVj64nLCkxyH8iJI9/19hUwjCfFdyGx/cw2upVLyOJzRe/iKxtz0suXV1hjM40nN9ai3 3zSQ== 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=FTeQNcQzbitXzFcO2J9EO4e7xIIvXcfqkM4ctkvNlsw=; b=wAeD0JHmakW0tBr3o1KQZwPT1LFVn5J191wsOrVJqQbrjOBdjwfde5z2ymNIq8mMcQ WFngFmpZH4FYl4mRNhtq+nK2nagi4gdrdN2jrtADFFn2er0+SVZn+AdZJ0S4W1aENYFn /5uz5BeceKzx21T/xCZqE3DbSniDK7jDJ9EnC3xDHftuIoFIXCPlymnWDbbcuQQwLgg9 YA9A738FPsRsEr2JURJuW47KT6DmoFTVeJwHYva0L3hni2QFC8Yf16Vlr5Uk1FRysBuw Gz9E56A29E1ndkhaS7ONzHvtTlp7E4RD+SLhIfKxPrA5371YiZsgTX3daY7uRYxtbXmm Dv7w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=axFDThBC; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 20-20020a630a14000000b00517f7c24664si1890868pgk.491.2023.04.20.08.21.50; Thu, 20 Apr 2023 08:22:15 -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=@kernel.org header.s=k20201202 header.b=axFDThBC; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233650AbjDTPEB (ORCPT + 99 others); Thu, 20 Apr 2023 11:04:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51890 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232294AbjDTPD6 (ORCPT ); Thu, 20 Apr 2023 11:03:58 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 74F9B35AF; Thu, 20 Apr 2023 08:03:57 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 0688461559; Thu, 20 Apr 2023 15:03:57 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 60CAEC4339C; Thu, 20 Apr 2023 15:03:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1682003036; bh=rXpdM/PXidMZuxAWqMp5XA9iSJNFfEvU4AkTCtcfBfE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=axFDThBCzxyW6grz0ekvb1o3N8C+1Qy9dh8n/bRTsqcUhcXxEoMMf7H5E1/WZbcNG uGWGzp+CW1Yjcig+UACPXOuAABUSf2Iqa6c2maOeq7zHb3IYbbJP8XyDt0g1t+1Eej i34yHW2Y8rrKMDP32blanK1LciufI8Vo9wu0xpjbIYgba0sGoxp6VdHi1bxEeRuE5h wbfPz2KU+ZXgOEdLoBlz3xVryd7utLfvzX0DKQrGkp9/s465TTZa5XBaltVSgvNcPx 8fw/RuHeWl7btNyptXdHAf1JuDOfAn0l43TybMKMIDKg34ZiSawuAph06SNIx1LNLp 09mYX427tY4TQ== Date: Thu, 20 Apr 2023 08:03:55 -0700 From: "Darrick J. Wong" To: Pankaj Raghav Cc: Hannes Reinecke , Matthew Wilcox , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, mcgrof@kernel.org, SSDR Gost Dev Subject: Re: [PATCH] mm/filemap: allocate folios according to the blocksize Message-ID: <20230420150355.GG360881@frogsfrogsfrogs> References: <20230414134908.103932-1-hare@suse.de> <2466fa23-a817-1dee-b89f-fcbeaca94a9e@samsung.com> <1c76a3fe-5b7a-6f22-78e1-da4a54497ecd@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1c76a3fe-5b7a-6f22-78e1-da4a54497ecd@samsung.com> X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 Thu, Apr 20, 2023 at 02:28:36PM +0200, Pankaj Raghav wrote: > On 2023-04-20 14:19, Hannes Reinecke wrote: > >> > >> **Questions on the future work**: > >> > >> As willy pointed out, we have to do this `order = mapping->host->i_blkbits - PAGE_SHIFT` in > >> many places. Should we pursue something that willy suggested: encapsulating order in the > >> mapping->flags as a next step?[1] > >> > >> > >> [1] https://lore.kernel.org/lkml/ZDty+PQfHkrGBojn@casper.infradead.org/ I wouldn't mind XFS gaining a means to control folio sizes, personally. At least that would make it easier to explore things like copy on write with large weird file allocation unit sizes (2MB, 28k, etc). > > > > Well ... really, not sure. > > Yes, continue updating buffer_heads would be a logical thing as it could be done incrementally. > > > > But really, the end-goal should be to move away from buffer_heads for fs and mm usage. So I wonder > > if we shouldn't rather look in that direction.. > > > Yeah, I understand that part. Hopefully, this will be discussed as a part of LSFMM. Agree. --D > > But the changes that are done in filemap and readahead needs to be done anyway irrespective of the > underlying aops right? Or Am I missing something. > > > Cheers, > > > > Hannes > >