linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: get rid of buffer_head use
Date: Thu, 6 Jun 2024 21:22:00 +0800	[thread overview]
Message-ID: <39ec8353-8f3e-45c6-b8a9-359ff96502f5@kernel.org> (raw)
In-Reply-To: <ZmGttup4xQM_jWky@casper.infradead.org>

On 2024/6/6 20:38, Matthew Wilcox wrote:
> On Thu, Jun 06, 2024 at 05:50:37PM +0800, Chao Yu wrote:
>> For later folio conversion.
> 
> What tree is this against?

Last dev-test branch of f2fs git tree, I guess it's a little behind
to linus' tree.

> 
>> @@ -3957,32 +3976,32 @@ static int read_raw_super_block(struct f2fs_sb_info *sbi,
>>   		return -ENOMEM;
>>   
>>   	for (block = 0; block < 2; block++) {
>> -		bh = sb_bread(sb, block);
>> -		if (!bh) {
>> +		page = read_mapping_page(sb->s_bdev->bd_inode->i_mapping,
>> +								block, NULL);
> 
> You need to use bd_mapping, not bd_inode->i_mapping (since May 21 in
> Linus' tree).

Will update it once f2fs codebase was rebased to linus' tree.

> 
> And I don't think there's much point in switching to pages as an
> intermediate step.  You may as well go straight to folios.
> 
> 		folio = read_mapping_folio(sb->s_bdev->bd_mapping, block, NULL);

Fine, let me work on this in v2.

Thanks,

> 


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2024-06-06 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06  9:50 [f2fs-dev] [PATCH] f2fs: get rid of buffer_head use Chao Yu
2024-06-06 12:38 ` Matthew Wilcox
2024-06-06 13:22   ` Chao Yu [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=39ec8353-8f3e-45c6-b8a9-359ff96502f5@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).