From: Randy Dunlap <randy.dunlap@oracle.com>
To: ratn.josh@gmail.com
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] Re-organization of PIDMAP_ENTRIES macro expansion
Date: Mon, 14 Jan 2008 09:20:35 -0800 [thread overview]
Message-ID: <20080114092035.321a64cc.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1200307835.2819.18.camel@life.india.kernelcorp.com>
On Mon, 14 Jan 2008 16:20:35 +0530 Ratnadeep Joshi wrote:
> This patch tries to re-organize the macro expansion of PIDMAP_ENTRIES
> (possibly) to a more clear one.
>
> Thanks,
> - Ratnadeep Joshi
>
> diff --git a/include/linux/pid_namespace.h
> b/include/linux/pid_namespace.h
> index 1689e28..06e3e99 100644
> --- a/include/linux/pid_namespace.h
> +++ b/include/linux/pid_namespace.h
> @@ -12,7 +12,7 @@ struct pidmap {
> void *page;
> };
>
> -#define PIDMAP_ENTRIES ((PID_MAX_LIMIT + 8*PAGE_SIZE -
> 1)/PAGE_SIZE/8)
> +#define PIDMAP_ENTRIES ((PID_MAX_LIMIT - 1)/PAGE_SIZE/8 + 1)
>
> struct pid_namespace {
> struct kref kref;
I beg to disagree. There is a very common (idiomatic) way for
doing this kind of calculation and the first/original expression
is in that form, although it's a little difficult to recognize.
This common formula lives in linux/kernel.h:
#define DIV_ROUND_UP(n,d) (((n) + (d) - 1) / (d))
where n is (AFAIK) numerator and d is divisor.
Example: One use of this is in linux/bitops.h:
#define BITS_TO_LONGS(nr) DIV_ROUND_UP(nr, BITS_PER_LONG)
This macro returns the number of longs that it takes to hold
'nr' bits. Expanded, it looks like:
nr_longs = (nr_bits + BITS_PER_LONG - 1) / BITS_PER_LONG;
The idiomatic formula handles boundary conditions very nicely.
Now for PIDMAP_ENTRIES, use 8 * PAGE_SIZE as the (d) part of
DIV_ROUND_UP() and you can see that it is done correctly.
---
~Randy
prev parent reply other threads:[~2008-01-14 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 10:50 [PATCH] Re-organization of PIDMAP_ENTRIES macro expansion Ratnadeep Joshi
2008-01-14 17:20 ` Randy Dunlap [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=20080114092035.321a64cc.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ratn.josh@gmail.com \
--cc=trivial@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