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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6AC9AEB64DC for ; Fri, 21 Jul 2023 06:26:34 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 0585A28019C; Fri, 21 Jul 2023 02:26:34 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 007A7280190; Fri, 21 Jul 2023 02:26:33 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E3A0228019C; Fri, 21 Jul 2023 02:26:33 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id D5C44280190 for ; Fri, 21 Jul 2023 02:26:33 -0400 (EDT) Received: from smtpin22.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id A0875120183 for ; Fri, 21 Jul 2023 06:26:33 +0000 (UTC) X-FDA: 81034635066.22.5D2C602 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by imf20.hostedemail.com (Postfix) with ESMTP id DC5021C0027 for ; Fri, 21 Jul 2023 06:26:31 +0000 (UTC) Authentication-Results: imf20.hostedemail.com; dkim=none; dmarc=none; spf=none (imf20.hostedemail.com: domain of hch@lst.de has no SPF policy when checking 213.95.11.211) smtp.mailfrom=hch@lst.de ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1689920792; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hie72xjAkKN4kSksvNLqig7sulKdIk+4lQa/sUfRRmE=; b=gFREzDAgxFcqFLbkiYfmPtgFW4zP4Bi23mD+NP4nJvnGMRDFuDRbr5k/1uacpatDNGpdB8 PS9K0Pn6Z3OuxSwEn2l0V15M9g5u+zSaR3CsnsA7OTiE7RoB9tYcQ6wjt6mAtu0S04YKYd H1bGvuJ5nMyKiPTk2ns3KcbjlqnQ6PA= ARC-Authentication-Results: i=1; imf20.hostedemail.com; dkim=none; dmarc=none; spf=none (imf20.hostedemail.com: domain of hch@lst.de has no SPF policy when checking 213.95.11.211) smtp.mailfrom=hch@lst.de ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1689920792; a=rsa-sha256; cv=none; b=72RBuFAWxBGP0WRIMufVMY0aOFxXztVKBPqACdxluFRl6vuB8f0iebBCGH714BKiiAGuGC wIgLAb8dyOA49S/JnFAAuQwjuN47kvK0FNniyXm9sBIAl6NjjUOEHOg7jsmMlsouxLxlVB ocmvdSqJ1JdJyLFvT/hZJQ3uuV7kHfE= Received: by verein.lst.de (Postfix, from userid 2407) id F15BC6732D; Fri, 21 Jul 2023 08:26:28 +0200 (CEST) Date: Fri, 21 Jul 2023 08:26:28 +0200 From: Christoph Hellwig To: Bob Peterson Cc: Christoph Hellwig , Jens Axboe , "Darrick J. Wong" , Andrew Morton , Matthew Wilcox , Christian Brauner , linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, cluster-devel Subject: Re: allow building a kernel without buffer_heads Message-ID: <20230721062628.GC20845@lst.de> References: <20230720140452.63817-1-hch@lst.de> <251d9862-e335-243e-d65a-c5538b4df253@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <251d9862-e335-243e-d65a-c5538b4df253@redhat.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Rspamd-Queue-Id: DC5021C0027 X-Rspam-User: X-Rspamd-Server: rspam05 X-Stat-Signature: 56n78rgyktpqoj41uxqr9j97norsm6cu X-HE-Tag: 1689920791-135323 X-HE-Meta: U2FsdGVkX1/oNPSc3tIShZPQWYfJkBKSAgIK9cKtlMulZHlATARbxpQfaqVj4n1Cut6jAHyJjt3KOCkVo8JXex9NSQ3GRkGkFvIxYMn7svoBCDxZ3IenEGDKS8RRaKVY5vzvUug/CJzAeIVWGkXVWShALUOOq75a51P+MngSkAz5N0PrZMnD2O/UZ7U7Rla7bjoct2V5WTJ7DWas5lZqaqy5TZjlSEPSHpa3Dj/oKZrY1HUvIX7+Y5PGfbGAKaJU+KbRKe215BrcW6UniDf+Q+hT4X9gMUy3uVJ+GHn4XHkGRlK/Cid8v9JRhdFscYsmPE0/epIN4N8D3O40kLcl6sWjrNw5XpNIXkd9lH7z7NB/iu7AzUiCZ4L/EZmW7NwDj/o7x/0Ihg+sC05StorVeR68DuHRkE3TBYjjuA49ECDGZgMxTg47eEzejX88z3PkAIuRqVdGn9k4Q5laHsDtbhfnfJ/CFQy5q1o68+Au6km+sgx/akMLgQGxSu/tlEPo9loGs3iUd49jis92qBYQqOimYcks+P7HHdA7hx2WC5Kteh8cUvt3Qur9Wrw+GWtkje3aP5/rNfFgdjXjXeF+DftH/GQ+D8y0yCUBdfU/m5rCsWFnKkLFjO4swsrz6B6yN92R9LKAsTibOGQfAsFHIxQobYjLDZEnvI3hEmQ/2E0uFkYy1KznQWnl8+sZQo7o4KY4xF7nDiHgefN6hyNwbPx98XEba+OeBCzujgDYbhCcDge0dVMMKRO7tZ9AbkwR26XEI2TI/xM3GVConK7lmT4fePzzJLwLJKcPJomALy0CmO8CRmzMmIpDA5te3byO79Yp6rudLszRYJcNCC2qrXMLUbetl3ezoSYABCUt8UW3Ur8iZMPbwKH6ps/68EvmdsMyIipkbL7TqE+61axo95s5xQKMIzRE+bI5LLMlSBrLklvjJRpT7CDkFAyejKzWxElE8c8d3D4/KDCm70Z lLsXx2pZ Kyp3pxR+nvp+DZppVNL5ImOtcAWEEIVTf2Q+Gm1B+uza7Ms/KDpp4U6clUbTdZpbBF9rMI4vwRmcK7fAAyYwsHb1CBJdrpBAjxvF4 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, Jul 20, 2023 at 09:51:30AM -0500, Bob Peterson wrote: > Gfs2 still uses buffer_heads to manage the metadata being pushed through > its journals. We've been reducing our dependency on them but eliminating > them altogether is a large and daunting task. We can still work toward that > goal, but it will take time. That's fine - gfs2 selects CONFIG_BUFFER_HEAD after this series and will be perfectly fine.