From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] allow building a kernel without buffer_heads
Date: Fri, 21 Jul 2023 08:26:28 +0200 [thread overview]
Message-ID: <20230721062628.GC20845@lst.de> (raw)
In-Reply-To: <251d9862-e335-243e-d65a-c5538b4df253@redhat.com>
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.
prev parent reply other threads:[~2023-07-21 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230720140452.63817-1-hch@lst.de>
2023-07-20 14:51 ` [Cluster-devel] allow building a kernel without buffer_heads Bob Peterson
2023-07-21 6:26 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230721062628.GC20845@lst.de \
--to=hch@lst.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).