linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: dsterba@suse.cz, David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/4] btrfs: tests: polish ifdefs around testing helper
Date: Tue, 11 Sep 2018 12:14:47 -0700	[thread overview]
Message-ID: <20180911191447.GA26631@vader> (raw)
In-Reply-To: <20180911092250.GC24025@twin.jikos.cz>

On Tue, Sep 11, 2018 at 11:22:51AM +0200, David Sterba wrote:
> On Mon, Sep 10, 2018 at 04:43:29PM -0700, Omar Sandoval wrote:
> > On Mon, Sep 10, 2018 at 07:22:31PM +0200, David Sterba wrote:
> > > Avoid the inline ifdefs and use two sections for self-tests enabled and
> > > disabled.
> > > 
> > > Signed-off-by: David Sterba <dsterba@suse.com>
> > > ---
> > >  fs/btrfs/ctree.h | 9 ++++++---
> > >  1 file changed, 6 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
> > > index 32d2fce4ac53..8dafc7bb6ad8 100644
> > > --- a/fs/btrfs/ctree.h
> > > +++ b/fs/btrfs/ctree.h
> > > @@ -3708,17 +3708,20 @@ static inline int btrfs_defrag_cancelled(struct btrfs_fs_info *fs_info)
> > >  #ifdef CONFIG_BTRFS_FS_RUN_SANITY_TESTS
> > >  void btrfs_test_inode_set_ops(struct inode *inode);
> > >  void btrfs_test_destroy_inode(struct inode *inode);
> > > -#endif
> > >  
> > >  static inline int btrfs_is_testing(struct btrfs_fs_info *fs_info)
> > >  {
> > > -#ifdef CONFIG_BTRFS_FS_RUN_SANITY_TESTS
> > >  	if (unlikely(test_bit(BTRFS_FS_STATE_DUMMY_FS_INFO,
> > >  			      &fs_info->fs_state)))
> > >  		return 1;
> > > -#endif
> > >  	return 0;
> > 
> > How about just:
> > 
> > 	return test_bit(BTRFS_FS_STATE_DUMMY_FS_INFO, &fs_info->fs_state);
> > 
> > We can probably get away without the unlikely() considering that no one
> > sane is going to run a kernel with CONFIG_BTRFS_FS_RUN_SANITY_TESTS in
> > production.
> 
> The unlikely can go away, sure.
> 
> I would still like to remove the test_bit call when tests are compiled
> out. There are about 10 calls to btrfs_is_testing in various core
> functions, followed by further statements. This would have a
> (negligible) runtime penalty but generates effectively unused code on
> production builds.
> 
> The static inline function returning 0 allows to optimize out the unused
> code, so smaller code, fewer inctructions, etc.

Absolutely, I just mean that the CONFIG_BTRFS_FS_RUN_SANITY_TESTS
version can be cleaner:

#ifdef CONFIG_BTRFS_FS_RUN_SANITY_TESTS
static inline int btrfs_is_testing(struct btrfs_fs_info *fs_info)
{
	return test_bit(BTRFS_FS_STATE_DUMMY_FS_INFO, &fs_info->fs_state);
}
#else
static inline int btrfs_is_testing(struct btrfs_fs_info *fs_info)
{
	return 0;
}
#endif

I find `if (1) return 1; else return 0;` really icky.

  reply	other threads:[~2018-09-12  0:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 17:22 [PATCH 0/4] Self-test cleanups David Sterba
2018-09-10 17:22 ` [PATCH 1/4] btrfs: tests: add separate stub for find_lock_delalloc_range David Sterba
2018-09-10 23:40   ` Omar Sandoval
2018-09-11  8:50     ` David Sterba
2018-09-14 16:38     ` [PATCH 1/4 v2] " David Sterba
2018-09-17 17:43       ` Omar Sandoval
2018-09-10 17:22 ` [PATCH 2/4] btrfs: tests: move testing members of struct btrfs_root to the end David Sterba
2018-09-10 23:37   ` Omar Sandoval
2018-09-10 17:22 ` [PATCH 3/4] btrfs: tests: group declarations of self-test helpers David Sterba
2018-09-10 23:41   ` Omar Sandoval
2018-09-10 17:22 ` [PATCH 4/4] btrfs: tests: polish ifdefs around testing helper David Sterba
2018-09-10 23:43   ` Omar Sandoval
2018-09-11  9:22     ` David Sterba
2018-09-11 19:14       ` Omar Sandoval [this message]
2018-09-14 14:20         ` David Sterba
2018-09-14 16:42         ` [PATCH 4/4 v2] " David Sterba
2018-09-17 17:40           ` Omar Sandoval

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=20180911191447.GA26631@vader \
    --to=osandov@osandov.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).