Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: simplify how first hit is passed to __btrfs_abort_transaction()
Date: Fri, 1 May 2026 07:54:19 +0930	[thread overview]
Message-ID: <0247f301-39ed-4e29-9a68-3a8ff3619006@suse.com> (raw)
In-Reply-To: <20260430141851.14332-1-dsterba@suse.com>



在 2026/4/30 23:48, David Sterba 写道:
> Optimize the btrfs_abort_transaction() for size as it (by our
> convention) must be put right after the error condition is detected.
> The exact file:line is reported so there's a portion that must be
> inlined. As this is cold code it bloats functions. In previous patch
> "btrfs: move transaction abort message to __btrfs_abort_transaction()"
> the error message was moved to the common helper, saving like 20KiB of
> btrfs.ko and several instructions per call site and some stack space.
> 
> There's little left to be optimized, we need to keep the atomic
> test_and_set_bit() and to convey that as 'first hit' to
> __btrfs_abort_transaction().
> 
> Right now it's a bool, which takes 8 bytes on stack for each call but
> it's 1 bit of information. We can encode that to some of the other
> parameters.
> 
> For that let's use the 'error' parameter, by convention it's negative
> errno so we can reliably detect if it's the first hit or a later error.
> Also the negation is usually implemented by a single instruction (NEG on
> x86_64) so the resulting object code is kept short.
> 
> This reduces btrfs.ko by 8K and stack in several functions by 8 bytes.
> 
> Cumulative effect with the other commit is -30K of btrfs.ko. While the
> encoding is an implementation detail, it's contained within the API.
> Making the transaction abort calls very light is desired.
> 
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
>   fs/btrfs/transaction.c | 13 ++++++++++++-
>   fs/btrfs/transaction.h | 15 +++++++++------
>   2 files changed, 21 insertions(+), 7 deletions(-)
> 
> diff --git a/fs/btrfs/transaction.c b/fs/btrfs/transaction.c
> index 01f66328966f..bbef3ae86ac4 100644
> --- a/fs/btrfs/transaction.c
> +++ b/fs/btrfs/transaction.c
> @@ -2723,12 +2723,23 @@ int btrfs_clean_one_deleted_snapshot(struct btrfs_fs_info *fs_info)
>    *
>    * We'll complete the cleanup in btrfs_end_transaction and
>    * btrfs_commit_transaction.
> + *
> + * Note: the parameter @error encodes whether the transactin abort was first hit
> + *       (setting the FS_ERROR state bit in btrfs_abort_transaction())
> + *       - positive number - first hit
> + *       - negative number - abort after it was already done
>    */
>   void __cold __btrfs_abort_transaction(struct btrfs_trans_handle *trans,
>   				      const char *function,
> -				      unsigned int line, int error, bool first_hit)
> +				      unsigned int line, int error)
>   {
>   	struct btrfs_fs_info *fs_info = trans->fs_info;
> +	bool first_hit = false;
> +
> +	if (error > 0) {
> +		error = -error;
> +		first_hit = true;
> +	}
>   
>   	WRITE_ONCE(trans->aborted, error);
>   	WRITE_ONCE(trans->transaction->aborted, error);
> diff --git a/fs/btrfs/transaction.h b/fs/btrfs/transaction.h
> index f1cb05460cec..e1d4e7330198 100644
> --- a/fs/btrfs/transaction.h
> +++ b/fs/btrfs/transaction.h
> @@ -243,20 +243,23 @@ static inline bool btrfs_abort_should_print_stack(int error)
>   }
>   
>   /*
> - * Call btrfs_abort_transaction as early as possible when an error condition is
> - * detected, that way the exact stack trace is reported for some errors.
> + * Call btrfs_abort_transaction() as early as possible when an error condition
> + * is detected, that way the exact stack trace is reported for some errors.
> + *
> + * Error number must be negative as it encodes wheather it's the first abort.

What about an ASSERT() for it?

It's not that rare to forgot the minus sign for immediately error code 
like "-EIO".

>    */
>   #define btrfs_abort_transaction(trans, error)		\

And I do not like to use macros when inlined function can be used.
There is no special requirement for things like #name, thus this can be 
converted to a regular static inline function.

Not sure how an static inlined version would affect the text section 
size though.

Thanks,
Qu
>   do {								\
> -	bool __first = false;					\
> +	int __error = (error);					\
> +								\
>   	/* Report first abort since mount */			\
>   	if (!test_and_set_bit(BTRFS_FS_STATE_TRANS_ABORTED,	\
>   			&((trans)->fs_info->fs_state))) {	\
> -		__first = true;					\
> +		__error = -__error;				\
>   		WARN_ON(btrfs_abort_should_print_stack(error));	\
>   	}							\
>   	__btrfs_abort_transaction((trans), __func__,		\
> -				  __LINE__, (error), __first);	\
> +				  __LINE__, __error);		\
>   } while (0)
>   
>   int btrfs_end_transaction(struct btrfs_trans_handle *trans);
> @@ -294,7 +297,7 @@ void btrfs_add_dropped_root(struct btrfs_trans_handle *trans,
>   void btrfs_trans_release_chunk_metadata(struct btrfs_trans_handle *trans);
>   void __cold __btrfs_abort_transaction(struct btrfs_trans_handle *trans,
>   				      const char *function,
> -				      unsigned int line, int error, bool first_hit);
> +				      unsigned int line, int error);
>   
>   int __init btrfs_transaction_init(void);
>   void __cold btrfs_transaction_exit(void);


  reply	other threads:[~2026-04-30 22:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 14:18 [PATCH] btrfs: simplify how first hit is passed to __btrfs_abort_transaction() David Sterba
2026-04-30 22:24 ` Qu Wenruo [this message]
2026-05-06 21:44   ` 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=0247f301-39ed-4e29-9a68-3a8ff3619006@suse.com \
    --to=wqu@suse.com \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@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