mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nilfs2: simplify nilfs_mdt_writeback()
Date: Mon, 05 Oct 2026 10:16:30 -0700	[thread overview]
Message-ID: <cba5c89f47212602dfb7e95c2d5104771356a432.camel@dubeyko.com> (raw)
In-Reply-To: <20261004233506.20802-1-konishi.ryusuke@gmail.com>

On Mon, 2026-10-05 at 08:31 +0900, Ryusuke Konishi wrote:
> The writepages() callback for metadata files, nilfs_mdt_writeback(),
> calls nilfs_mdt_write_folio() for each dirty folio via
> writeback_iter(),
> where read-only superblock checks, folio dirty state clearing on
> error,
> and triggering of the log writer via nilfs_construct_segment() are
> performed.  This helper function is used nowhere else.
> 
> Executing these operations per folio is inefficient:
> 
> - Checking if the filesystem has fallen back to read-only mode is
>   repeated redundantly.
> 
> - Calling nilfs_construct_segment() inside the per-folio loop causes
>   redundant log writer invocations for a single sync request, where
> only
>   the first invocation performs actual log writing.
> 
> Unfold nilfs_mdt_write_folio() into nilfs_mdt_writeback() and
> consolidate
> these operations at the function level.  The read-only check is moved
> to
> the top of nilfs_mdt_writeback(), replacing per-folio
> nilfs_clear_folio_dirty() calls with a single
> nilfs_clear_dirty_pages()
> call to discard dirty pages across the mapping at once. 
> Additionally,
> nilfs_construct_segment() is invoked once when 'sync_mode' is
> WB_SYNC_ALL
> and the mapping is tagged dirty.
> 
> With these operations consolidated outside the loop, the remaining
> per-folio actions (calling folio_redirty_for_writepage() on already
> dirty folios and unlocking them) serve no purpose, so the folio
> iteration
> itself is removed.
> 
> Signed-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>
> ---
> Viacheslav,
> 
> Please add this to the queue for the next cycle.
> 
> This refactors the metadata file writeback callback function,
> restructuring an inefficient legacy function organization rooted in
> the era of aops->writepage() to align with aops->writepages().
> 
> Thanks,
> Ryusuke Konishi
> 
>  fs/nilfs2/mdt.c | 40 +++++++++++-----------------------------
>  1 file changed, 11 insertions(+), 29 deletions(-)
> 
> diff --git a/fs/nilfs2/mdt.c b/fs/nilfs2/mdt.c
> index b50c88b65183..77dc2be2ce65 100644
> --- a/fs/nilfs2/mdt.c
> +++ b/fs/nilfs2/mdt.c
> @@ -391,51 +391,33 @@ int nilfs_mdt_fetch_dirty(struct inode *inode)
>  	return test_bit(NILFS_I_DIRTY, &ii->i_state);
>  }
>  
> -static int nilfs_mdt_write_folio(struct folio *folio,
> +static int nilfs_mdt_writeback(struct address_space *mapping,
>  		struct writeback_control *wbc)
>  {
> -	struct inode *inode = folio->mapping->host;
> -	struct super_block *sb;
> +	struct inode *inode = mapping->host;
>  	int err = 0;
>  
> -	if (inode && sb_rdonly(inode->i_sb)) {
> +	if (!inode)
> +		return 0;
> +
> +	if (sb_rdonly(inode->i_sb)) {
>  		/*
>  		 * It means that filesystem was remounted in read-
> only
>  		 * mode because of error or metadata corruption. But
> we
>  		 * have dirty folios that try to be flushed in
> background.
> -		 * So, here we simply discard this dirty folio.
> +		 * So, here we simply discard these dirty folios.
>  		 */
> -		nilfs_clear_folio_dirty(folio, false);
> -		folio_unlock(folio);
> +		nilfs_clear_dirty_pages(mapping, false);
>  		return -EROFS;
>  	}
>  
> -	folio_redirty_for_writepage(wbc, folio);
> -	folio_unlock(folio);
> -
> -	if (!inode)
> -		return 0;
> -
> -	sb = inode->i_sb;
> -
> -	if (wbc->sync_mode == WB_SYNC_ALL)
> -		err = nilfs_construct_segment(sb);
> +	if (wbc->sync_mode == WB_SYNC_ALL &&
> +		mapping_tagged(mapping, PAGECACHE_TAG_DIRTY))
> +		err = nilfs_construct_segment(inode->i_sb);
>  
>  	return err;
>  }
>  
> -static int nilfs_mdt_writeback(struct address_space *mapping,
> -		struct writeback_control *wbc)
> -{
> -	struct folio *folio = NULL;
> -	int error;
> -
> -	while ((folio = writeback_iter(mapping, wbc, folio,
> &error)))
> -		error = nilfs_mdt_write_folio(folio, wbc);
> -
> -	return error;
> -}
> -
>  static const struct address_space_operations def_mdt_aops = {
>  	.dirty_folio		= block_dirty_folio,
>  	.invalidate_folio	= block_invalidate_folio,

Applied.

Thanks,
Slava.

      reply	other threads:[~2026-10-05 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 23:31 Ryusuke Konishi
2026-10-05 17:16 ` Viacheslav Dubeyko [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=cba5c89f47212602dfb7e95c2d5104771356a432.camel@dubeyko.com \
    --to=slava@dubeyko.com \
    --cc=konishi.ryusuke@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.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

all inboxes | Powered by JetHome®