From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
containers@lists.linux-foundation.org
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [RFC] Restrict size of page_cgroup->flags
Date: Wed, 6 Oct 2010 19:53:14 +0530 [thread overview]
Message-ID: <20101006142314.GG4195@balbir.in.ibm.com> (raw)
I propose restricting page_cgroup.flags to 16 bits. The patch for the
same is below. Comments?
Restrict the bits usage in page_cgroup.flags
From: Balbir Singh <balbir@linux.vnet.ibm.com>
Restricting the flags helps control growth of the flags unbound.
Restriciting it to 16 bits gives us the possibility of merging
cgroup id with flags (atomicity permitting) and saving a whole
long word in page_cgroup
Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
---
include/linux/page_cgroup.h | 3 +++
mm/page_cgroup.c | 1 +
2 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/include/linux/page_cgroup.h b/include/linux/page_cgroup.h
index 872f6b1..10c37b4 100644
--- a/include/linux/page_cgroup.h
+++ b/include/linux/page_cgroup.h
@@ -44,8 +44,11 @@ enum {
PCG_FILE_WRITEBACK, /* page is under writeback */
PCG_FILE_UNSTABLE_NFS, /* page is NFS unstable */
PCG_MIGRATION, /* under page migration */
+ PCG_MAX_NR,
};
+#define PCG_MAX_BIT_SIZE 16
+
#define TESTPCGFLAG(uname, lname) \
static inline int PageCgroup##uname(struct page_cgroup *pc) \
{ return test_bit(PCG_##lname, &pc->flags); }
diff --git a/mm/page_cgroup.c b/mm/page_cgroup.c
index 5bffada..e16ad2e 100644
--- a/mm/page_cgroup.c
+++ b/mm/page_cgroup.c
@@ -258,6 +258,7 @@ void __init page_cgroup_init(void)
unsigned long pfn;
int fail = 0;
+ BUILD_BUG_ON(PCG_MAX_NR >= PCG_MAX_BIT_SIZE);
if (mem_cgroup_disabled())
return;
--
Three Cheers,
Balbir
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2010-10-06 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 14:23 Balbir Singh [this message]
2010-10-06 23:58 ` [RFC] Restrict size of page_cgroup->flags KAMEZAWA Hiroyuki
2010-10-07 3:12 ` Balbir Singh
2010-10-07 3:18 ` KAMEZAWA Hiroyuki
2010-10-07 3:56 ` Balbir Singh
2010-10-07 4:22 ` KAMEZAWA Hiroyuki
2010-10-07 5:31 ` Balbir Singh
2010-10-07 5:39 ` KAMEZAWA Hiroyuki
2010-10-07 5:44 ` Daisuke Nishimura
2010-10-07 0:54 ` Daisuke Nishimura
2010-10-07 3:14 ` Balbir Singh
2010-10-07 3:47 ` Daisuke Nishimura
2010-10-07 4:08 ` Balbir Singh
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=20101006142314.GG4195@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).