From: Matthew Wilcox <email@example.com> To: Hannes Reinecke <firstname.lastname@example.org> Cc: email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: [RFC] synchronous readpage for buffer_heads Date: Fri, 23 Oct 2020 12:42:20 +0100 Message-ID: <20201023114220.GY20115@casper.infradead.org> (raw) In-Reply-To: <firstname.lastname@example.org> On Fri, Oct 23, 2020 at 08:22:07AM +0200, Hannes Reinecke wrote: > On 10/22/20 5:22 PM, Matthew Wilcox wrote: > Hmm. You are aware, of course, that hch et al are working on replacing bhs > with iomap, right? $ git shortlog --author=Wilcox origin/master -- fs/iomap |head -1 Matthew Wilcox (Oracle) (17): But actually, I don't see anyone working on a mass migration of filesystems from either using BHs directly or using the mpage code to using iomap. I have a summer student for next summer who I'm going to let loose on this problem, but I fear buffer_heads will be with us for a long time to come. I mean, who's going to convert reiserfs to iomap? $ git log --no-merges --since=2015-01-01 origin/master fs/reiserfs |grep -c ^comm 130 Not exactly a thriving development community. It doesn't even support fallocate. > So wouldn't it be more useful to concentrate on the iomap code, and ensure > that _that_ is working correctly? Did that one first, then did mpage_readpage(), now I've moved on to block_read_full_page(). Now I'm going to go back and redo iomap with everything I learned doing block_read_full_page(). It's going to use blk_completion.
prev parent reply index Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-22 15:22 Matthew Wilcox 2020-10-23 6:22 ` Hannes Reinecke 2020-10-23 11:42 ` Matthew Wilcox [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=20201023114220.GY20115@casper.infradead.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
Linux-Fsdevel Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-fsdevel/0 linux-fsdevel/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-fsdevel linux-fsdevel/ https://lore.kernel.org/linux-fsdevel \ firstname.lastname@example.org public-inbox-index linux-fsdevel Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-fsdevel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git