From: Andreas Dilger <adilger@dilger.ca>
To: Eric Biggers <ebiggers@google.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4 <linux-ext4@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blockgroup_lock.h: simplify definition of NR_BG_LOCKS
Date: Wed, 14 Sep 2016 15:09:30 -0600 [thread overview]
Message-ID: <3F033C47-E636-42D1-AFCD-FCBCBF795ED4@dilger.ca> (raw)
In-Reply-To: <1473881320-123184-1-git-send-email-ebiggers@google.com>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
On Sep 14, 2016, at 1:28 PM, Eric Biggers <ebiggers@google.com> wrote:
>
> We can use ilog2() to more easily produce the desired NR_BG_LOCKS. This
> works because ilog2() is evaluated at compile-time when its argument is
> a compile-time constant.
>
> I did not change the chosen NR_BG_LOCKS values.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
> ---
> include/linux/blockgroup_lock.h | 22 ++--------------------
> 1 file changed, 2 insertions(+), 20 deletions(-)
>
> diff --git a/include/linux/blockgroup_lock.h b/include/linux/blockgroup_lock.h
> index 61b583d..225bdb7 100644
> --- a/include/linux/blockgroup_lock.h
> +++ b/include/linux/blockgroup_lock.h
> @@ -10,28 +10,10 @@
> #include <linux/cache.h>
>
> #ifdef CONFIG_SMP
> -
> -/*
> - * We want a power-of-two. Is there a better way than this?
> - */
> -
> -#if NR_CPUS >= 32
> -#define NR_BG_LOCKS 128
> -#elif NR_CPUS >= 16
> -#define NR_BG_LOCKS 64
> -#elif NR_CPUS >= 8
> -#define NR_BG_LOCKS 32
> -#elif NR_CPUS >= 4
> -#define NR_BG_LOCKS 16
> -#elif NR_CPUS >= 2
> -#define NR_BG_LOCKS 8
> +#define NR_BG_LOCKS (4 << ilog2(NR_CPUS < 32 ? NR_CPUS : 32))
> #else
> -#define NR_BG_LOCKS 4
> -#endif
> -
> -#else /* CONFIG_SMP */
> #define NR_BG_LOCKS 1
> -#endif /* CONFIG_SMP */
> +#endif
>
> struct bgl_lock {
> spinlock_t lock;
> --
> 2.8.0.rc3.226.g39d4020
>
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2016-09-14 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 19:28 Eric Biggers
2016-09-14 21:09 ` Andreas Dilger [this message]
2016-09-15 22:29 ` Theodore Ts'o
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=3F033C47-E636-42D1-AFCD-FCBCBF795ED4@dilger.ca \
--to=adilger@dilger.ca \
--cc=ebiggers@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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®