linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kairui Song <ryncsn@gmail.com>
To: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	linux-mm@kvack.org,  Andrew Morton <akpm@linux-foundation.org>,
	"Huang, Ying" <ying.huang@intel.com>,
	 Chris Li <chrisl@kernel.org>, Barry Song <v-songbaohua@oppo.com>,
	 Ryan Roberts <ryan.roberts@arm.com>, Neil Brown <neilb@suse.de>,
	Minchan Kim <minchan@kernel.org>,
	 Hugh Dickins <hughd@google.com>,
	David Hildenbrand <david@redhat.com>,
	Yosry Ahmed <yosryahmed@google.com>,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-nilfs@vger.kernel.org
Subject: Re: [PATCH v3 02/12] nilfs2: drop usage of page_index
Date: Tue, 30 Apr 2024 23:27:13 +0800	[thread overview]
Message-ID: <CAMgjq7D0HwiD-v_HCQWkGNoK2hWzL-B-1u0zRAp9xR6p+HfiUQ@mail.gmail.com> (raw)
In-Reply-To: <CAKFNMokDR7oQxDH8WeUeJKm6GLDo54AnByYXxdAWHjiFeGWEwA@mail.gmail.com>

On Tue, Apr 30, 2024 at 4:01 AM Ryusuke Konishi
<konishi.ryusuke@gmail.com> wrote:
>
> On Tue, Apr 30, 2024 at 4:38 AM Matthew Wilcox wrote:
> >
> > On Tue, Apr 30, 2024 at 04:28:41AM +0900, Ryusuke Konishi wrote:
> > > On Tue, Apr 30, 2024 at 4:22 AM Kairui Song <ryncsn@gmail.com> wrote:
> > > >
> > > > On Tue, Apr 30, 2024 at 3:14 AM Matthew Wilcox <willy@infradead.org> wrote:
> > > > >
> > > > > On Tue, Apr 30, 2024 at 03:04:50AM +0800, Kairui Song wrote:
> > > > > > From: Kairui Song <kasong@tencent.com>
> > > > > >
> > > > > > page_index is only for mixed usage of page cache and swap cache, for
> > > > > > pure page cache usage, the caller can just use page->index instead.
> > > > > >
> > > > > > It can't be a swap cache page here (being part of buffer head),
> > > > > > so just drop it, also convert it to use folio.
> > > > > >
> > > > > > Signed-off-by: Kairui Song <kasong@tencent.com>
> > > > > > Cc: Ryusuke Konishi <konishi.ryusuke@gmail.com>
> > > > > > Cc: linux-nilfs@vger.kernel.org
> > > > > > ---
> > > > > >  fs/nilfs2/bmap.c | 5 ++---
> > > > > >  1 file changed, 2 insertions(+), 3 deletions(-)
> > > > > >
> > > > > > diff --git a/fs/nilfs2/bmap.c b/fs/nilfs2/bmap.c
> > > > > > index 383f0afa2cea..f4e5df0cd720 100644
> > > > > > --- a/fs/nilfs2/bmap.c
> > > > > > +++ b/fs/nilfs2/bmap.c
> > > > > > @@ -453,9 +453,8 @@ __u64 nilfs_bmap_data_get_key(const struct nilfs_bmap *bmap,
> > > > > >       struct buffer_head *pbh;
> > > > > >       __u64 key;
> > > > > >
> > > > > > -     key = page_index(bh->b_page) << (PAGE_SHIFT -
> > > > > > -                                      bmap->b_inode->i_blkbits);
> > > > > > -     for (pbh = page_buffers(bh->b_page); pbh != bh; pbh = pbh->b_this_page)
> > > > > > +     key = bh->b_folio->index << (PAGE_SHIFT - bmap->b_inode->i_blkbits);
> > > > > > +     for (pbh = folio_buffers(bh->b_folio); pbh != bh; pbh = pbh->b_this_page)
> > > > > >               key++;
> > > > > >
> > > > > >       return key;
> > > > >
> > > > > Why isn't this entire function simply:
> > > > >
> > > > >         return bh->b_blocknr;
> > > > >
> > > >
> > > > Nice idea, I didn't plan for extra clean up and test for fs code, but
> > > > this might be OK to have, will check it.
> > >
> > > Wait a minute.
> > >
> > > This function returns a key that corresponds to the cache offset of
> > > the data block, not the disk block number.
> > >
> > > Why is returning to bh->b_blocknr an alternative ?
> > > Am I missing something?
> >
> > Sorry, I forgot how b_blocknr was used.  What I meant was:
> >
> >         u64 key = bh->b_folio->index << (PAGE_SHIFT - bmap->b_inode->i_blkbits);
> >
> >         return key + bh_offset(bh) >> bmap->b_inode->i_blkbits;
> >
> > The point is to get rid of the loop.  We could simplify this (and make
> > it ready for bs>PS) by doing:
> >
> >         loff_t pos = folio_pos(bh->b_folio) + bh_offset(bh);
> >         return pos >> bmap->b_inode->i_blkbits;
>
> I see, I understand the idea that it would be better to eliminate the loop.
>
> The above conversion looks fine.
> What are you going to do, Kairui ?

Hi, I'd like to remove the loop as Matthew suggested, that will make
the code cleaner.
I'm not very familiar with this part so I'll check related code first
for double check, won't take long though.

> Thanks,
> Ryusuke Konishi

      reply	other threads:[~2024-04-30 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240429190500.30979-1-ryncsn@gmail.com>
2024-04-29 19:04 ` [PATCH v3 02/12] nilfs2: drop usage of page_index Kairui Song
2024-04-29 19:14   ` Matthew Wilcox
2024-04-29 19:22     ` Kairui Song
2024-04-29 19:28       ` Ryusuke Konishi
2024-04-29 19:38         ` Matthew Wilcox
2024-04-29 20:01           ` Ryusuke Konishi
2024-04-30 15:27             ` Kairui Song [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=CAMgjq7D0HwiD-v_HCQWkGNoK2hWzL-B-1u0zRAp9xR6p+HfiUQ@mail.gmail.com \
    --to=ryncsn@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=chrisl@kernel.org \
    --cc=david@redhat.com \
    --cc=hughd@google.com \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=neilb@suse.de \
    --cc=ryan.roberts@arm.com \
    --cc=v-songbaohua@oppo.com \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.com \
    --cc=yosryahmed@google.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
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).