From: Ratnadeep Joshi <ratn.josh@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: trivial@kernel.org, akpm@linux-foundation.org
Subject: [PATCH] Re-organization of PIDMAP_ENTRIES macro expansion
Date: Mon, 14 Jan 2008 16:20:35 +0530 [thread overview]
Message-ID: <1200307835.2819.18.camel@life.india.kernelcorp.com> (raw)
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;
next reply other threads:[~2008-01-14 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 10:50 Ratnadeep Joshi [this message]
2008-01-14 17:20 ` [PATCH] Re-organization of PIDMAP_ENTRIES macro expansion Randy Dunlap
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=1200307835.2819.18.camel@life.india.kernelcorp.com \
--to=ratn.josh@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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