Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2119345rwd; Fri, 26 May 2023 01:52:52 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7aD4QSqwQGXGq2ig6Ml0+51MDhfi/cw1sdJ5hoLbavjVZW4CyhHvdm7JrS9+qEh9TDZIsB X-Received: by 2002:a05:6a00:21d2:b0:64f:4706:3122 with SMTP id t18-20020a056a0021d200b0064f47063122mr2291150pfj.30.1685091172412; Fri, 26 May 2023 01:52:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685091172; cv=none; d=google.com; s=arc-20160816; b=va4tGHrdI5cW/klK44KjuSYlNM5ONrEjLQ77496B96Q1h3RuxJNc1PqTqG5TDVd3GA d09IZbIAqVhzKk9Z7e7rLg48ipGSzsSVjnsldKhFr990J98ljosdr1VLQ5lfxn9kPI6x 3GywzlOJztXPIz1PdYU5b9vvJR00p8g96lDEznH99cWJmTXL3GFEromvf1ZPz/bO/Jtd EkZTui2kZemoDTTBu+7i2MXQmlarKr2V6T4soV6gJnAwPqHwQpHpecV0b1EFJW9DCb6q N0567eI4kyPmypQKcf8lUyUIvZk07II0veVXJWnuxZsexn9lPF4V+B0Fc4IzV3fHxnMV NsPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=cU4HbZ0Ihk69KMRkjUWIN8WBPWiQau/75Wx/UKV6Xy8=; b=PymOZzID3FRJGN+Ga9IkvbdZXOStqR+yiYKxaOYmD59GB4R0olFVLjvs6HmE/wIlgq AS53q21ggCdGdg+GwOcbU1z1XOjUPNKWGyaSaPQqtna5rTmg5/RBR0bKJ95oi+ZUv6d3 is7PJD7Odzo9JHcu67HNGYw8PVnGAP3uYV6krO8kB8NYwV+k+O2FP1pj1OTrMgtGd+Ok 8P85xqZ7ZWRro6yDXyOU8/asH4m0+awI36OKPLpyWI+tOtr/YDTOVGf0hO5ZsRhWHsFA QzqfmBVSlVQlYRYz8tiV4q0wpKGN4rypWaXgYlFpcvxMebTDQDdxZRmhmxyZXVh6BR56 7sFA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=bombadil.20210309 header.b=NbqKOjNG; 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 c6-20020a6566c6000000b00537669c7a90si837857pgw.844.2023.05.26.01.52.37; Fri, 26 May 2023 01:52:52 -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=bombadil.20210309 header.b=NbqKOjNG; 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 S242745AbjEZIft (ORCPT + 99 others); Fri, 26 May 2023 04:35:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38472 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242600AbjEZIfs (ORCPT ); Fri, 26 May 2023 04:35:48 -0400 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 58276199; Fri, 26 May 2023 01:35:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=cU4HbZ0Ihk69KMRkjUWIN8WBPWiQau/75Wx/UKV6Xy8=; b=NbqKOjNGXmKVkdSnQezuWV1eT5 shzgQn36kaoEabnbYb/Jyz3Rdfyo4i9Gt9NcFEgBW4SxCR9JG+o+jSKnUKh34k8rrj8nhlDQulx6y 6VreloRZ4j6ECTgnH6aVsJIOwYtIqjD5EVkDYaakhcl9aFDyVUPVL/7qPbXwjDPiuKZjBAJ0h2p/c AeN+fmkiyu4Cusz7HUAP0Hz6pvjMNSt5HsMgL8MBhbG43QEg+Ri3e8GndeuvIjNy1idYUYW6cxIiL jsCIs6TkJFVD5KST6G7qRiRVkM5o6ra1UpwTs2oEuwtb9GLGqQOM7RcaspSqneNmqabaORhr7WwZy Stg1KBDw==; Received: from mcgrof by bombadil.infradead.org with local (Exim 4.96 #2 (Red Hat Linux)) id 1q2Sv2-001cm2-0Z; Fri, 26 May 2023 08:35:28 +0000 Date: Fri, 26 May 2023 01:35:28 -0700 From: Luis Chamberlain To: Christoph Hellwig Cc: hughd@google.com, akpm@linux-foundation.org, willy@infradead.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: Sender: Luis Chamberlain X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,HEADER_FROM_DIFFERENT_DOMAINS, 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 01:28:03AM -0700, Christoph Hellwig wrote: > On Fri, May 26, 2023 at 01:18:19AM -0700, Luis Chamberlain wrote: > > On Fri, May 26, 2023 at 01:14:55AM -0700, Christoph Hellwig wrote: > > > On Fri, May 26, 2023 at 12:55:44AM -0700, Luis Chamberlain wrote: > > > > This is an initial attempt to add support for block size > PAGE_SIZE for tmpfs. > > > > > > The concept of a block size doesn't make any sense for tmpfs. What > > > are you actually trying to do here? > > > > More of helping to test high order folios for tmpfs. Swap for instance > > would be one thing we could use to test. > > I'm still not sure where the concept of a block size would come in here. From a filesystem perspective that's what we call it as well today, and tmpfs implements a simple one, just that indeed this just a high order folio support. The languge for blocksize was used before my patches for the sb->s_blocksize and sb->s_blocksize_bits. Even for shmem_statfs() buf->f_bsize. I understand we should move the sb->s_blocksize to the block_device and use the page order for address_space, but we can't negate the existing stuff there immediately. Luis