From: David Sterba <dsterba@suse.cz>
To: Boris Burkov <boris@bur.io>
Cc: Goldwyn Rodrigues <rgoldwyn@suse.de>,
linux-btrfs@vger.kernel.org,
Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH 3/4] btrfs: convert relocate_one_page() to relocate_one_folio()
Date: Mon, 22 Jan 2024 21:53:32 +0100 [thread overview]
Message-ID: <20240122205332.GZ31555@twin.jikos.cz> (raw)
In-Reply-To: <20240118214347.GC1356080@zen.localdomain>
On Thu, Jan 18, 2024 at 01:43:47PM -0800, Boris Burkov wrote:
> On Thu, Jan 18, 2024 at 01:46:39PM -0600, Goldwyn Rodrigues wrote:
> > From: Goldwyn Rodrigues <rgoldwyn@suse.com>
> > -static int relocate_one_page(struct inode *inode, struct file_ra_state *ra,
> > +static int relocate_one_folio(struct inode *inode, struct file_ra_state *ra,
> > const struct file_extent_cluster *cluster,
> > - int *cluster_nr, unsigned long page_index)
> > + int *cluster_nr, unsigned long index)
> > {
> > struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb);
> > u64 offset = BTRFS_I(inode)->index_cnt;
> > const unsigned long last_index = (cluster->end - offset) >> PAGE_SHIFT;
> > gfp_t mask = btrfs_alloc_write_mask(inode->i_mapping);
> > - struct page *page;
> > - u64 page_start;
> > - u64 page_end;
> > + struct folio *folio;
> > + u64 start;
> > + u64 end;
>
> This patch throws out this function labelling the start/index/end with
> 'page_' which I think was pretty useful given the other starts/ends like
> 'extent_' and 'clamped_'. Namespacing the indices makes the code easier
> to follow, IMO.
With all the other prefixes around I agree that keeping folio_ (as
replacement of page_) would be useful.
next prev parent reply other threads:[~2024-01-22 20:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1705605787.git.rgoldwyn@suse.com>
2024-01-18 19:46 ` [PATCH 1/4] btrfs: Use IS_ERR() instead of checking folio for NULL Goldwyn Rodrigues
2024-01-18 21:31 ` Boris Burkov
2024-01-19 14:53 ` David Sterba
2024-01-19 14:58 ` Goldwyn Rodrigues
2024-01-18 19:46 ` [PATCH 2/4] btrfs: page to folio conversion: prealloc_file_extent_cluster() Goldwyn Rodrigues
2024-01-18 21:34 ` Boris Burkov
2024-01-22 20:44 ` David Sterba
2024-01-18 19:46 ` [PATCH 3/4] btrfs: convert relocate_one_page() to relocate_one_folio() Goldwyn Rodrigues
2024-01-18 21:43 ` Boris Burkov
2024-01-22 20:53 ` David Sterba [this message]
2024-01-22 20:52 ` David Sterba
2024-01-23 16:36 ` Goldwyn Rodrigues
2024-01-18 19:46 ` [PATCH 4/4] btrfs: page to folio conversion in put_file_data() Goldwyn Rodrigues
2024-01-18 21:48 ` Boris Burkov
2024-01-22 20:55 ` David Sterba
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=20240122205332.GZ31555@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=boris@bur.io \
--cc=linux-btrfs@vger.kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rgoldwyn@suse.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