linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Matthew Wilcox <willy@infradead.org>
Cc: "lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	linux-mm@kvack.org,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] Sunsetting buffer_heads
Date: Wed, 12 Apr 2023 15:27:18 +0200	[thread overview]
Message-ID: <f6eba66c-1698-0002-8329-6fe6d216c5f4@suse.de> (raw)
In-Reply-To: <ZDavMfPMwEeWa4uQ@casper.infradead.org>

On 4/12/23 15:16, Matthew Wilcox wrote:
> On Wed, Apr 12, 2023 at 12:18:29PM +0200, Hannes Reinecke wrote:
>> Ceterum censeo ...
>>
>> Having looked at implementing large blocksizes I constantly get bogged down
>> by buffer_heads and being as they are intricately linked into filesystems
>> and mm.
>>
>> And also everyone seems to have agreed to phase out buffer_heads eventually.
>>
>> So maybe it's time to start discussing exactly _how_ this could be done.
>> And LSF/MM seems to be the idea location for it.
>>
>> So far I've came across the following issues:
>>
>> - reading superblocks / bread(): maybe convert to ->read_folio() ?
>> - bh_lru and friends (maybe pointless once bread() has been converted)
>> - How to handle legacy filesystems still running on buffer_heads
>>
>> I'm sure this is an incomplete list, and I'm equally sure that several
>> people have their own ideas what should or need to be done.
>>
>> So this BOF will be about collecting these ideas and coming up with a design
>> how we can deprecated buffer_heads.
> 
> Might be worth reviewing this thread:
> 
> https://lore.kernel.org/linux-fsdevel/20230129044645.3cb2ayyxwxvxzhah@garbanzo/

A-ha. So I'm not alone.

Please count me in in that session.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		           Kernel Storage Architect
hare@suse.de			                  +49 911 74053 688
SUSE Software Solutions Germany GmbH, Frankenstr. 146, 90461 Nürnberg
Managing Directors: I. Totev, A. Myers, A. McDonald, M. B. Moerman
(HRB 36809, AG Nürnberg)



      reply	other threads:[~2023-04-12 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 10:18 Hannes Reinecke
2023-04-12 13:16 ` Matthew Wilcox
2023-04-12 13:27   ` Hannes Reinecke [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=f6eba66c-1698-0002-8329-6fe6d216c5f4@suse.de \
    --to=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=willy@infradead.org \
    /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