From: Andrea Righi <righi.andrea@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: balbir@linux.vnet.ibm.com, linux-mm@kvack.org,
skumar@linux.vnet.ibm.com, yamamoto@valinux.co.jp,
menage@google.com, lizf@cn.fujitsu.com,
linux-kernel@vger.kernel.org, xemul@openvz.org,
kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [-mm][PATCH 2/4] Setup the memrlimit controller (v5)
Date: Wed, 11 Jun 2008 22:17:12 +0200 [thread overview]
Message-ID: <485032C8.4010001@gmail.com> (raw)
In-Reply-To: <20080611121510.d91841a3.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 11 Jun 2008 19:10:40 +0200 (MEST)
> Andrea Righi <righi.andrea@gmail.com> wrote:
>
>> Balbir Singh wrote:
>>> +static int memrlimit_cgroup_write_strategy(char *buf, unsigned long long *tmp)
>>> +{
>>> + *tmp = memparse(buf, &buf);
>>> + if (*buf != '\0')
>>> + return -EINVAL;
>>> +
>>> + *tmp = PAGE_ALIGN(*tmp);
>>> + return 0;
>>> +}
>> We shouldn't use PAGE_ALIGN() here, otherwise we limit the address space
>> to 4GB on 32-bit architectures (that could be reasonable, because this
>> is a per-cgroup limit and not per-process).
>>
>> Signed-off-by: Andrea Righi <righi.andrea@gmail.com>
>> ---
>> mm/memrlimitcgroup.c | 4 +++-
>> 1 files changed, 3 insertions(+), 1 deletions(-)
>>
>> diff --git a/mm/memrlimitcgroup.c b/mm/memrlimitcgroup.c
>> index 9a03d7d..2d42ff3 100644
>> --- a/mm/memrlimitcgroup.c
>> +++ b/mm/memrlimitcgroup.c
>> @@ -29,6 +29,8 @@
>> #include <linux/res_counter.h>
>> #include <linux/memrlimitcgroup.h>
>>
>> +#define PAGE_ALIGN64(addr) (((((addr)+PAGE_SIZE-1))>>PAGE_SHIFT)<<PAGE_SHIFT)
>> +
>> struct cgroup_subsys memrlimit_cgroup_subsys;
>>
>> struct memrlimit_cgroup {
>> @@ -124,7 +126,7 @@ static int memrlimit_cgroup_write_strategy(char *buf, unsigned long long *tmp)
>> if (*buf != '\0')
>> return -EINVAL;
>>
>> - *tmp = PAGE_ALIGN(*tmp);
>> + *tmp = PAGE_ALIGN64(*tmp);
>> return 0;
>> }
>>
>
> I don't beleive the change is needed.
>
> #define PAGE_ALIGN(addr) (((addr)+PAGE_SIZE-1)&PAGE_MASK)
>
> that implementation will behaved as desired when passed a 64-bit addr?
If I'm not doing something wrong, here is what happens on my i386 box:
$ uname -m
i686
$ cat 64-bit-page-align.c
#include <stdio.h>
#include <asm/page.h>
#define PAGE_ALIGN(addr) (((addr)+PAGE_SIZE-1)&PAGE_MASK)
#define PAGE_ALIGN64(addr) (((((addr)+PAGE_SIZE-1))>>PAGE_SHIFT)<<PAGE_SHIFT)
#define SIZE ((1ULL << 32) - 1)
int main(int argc, char **argv)
{
unsigned long long good, bad;
good = (unsigned long long)PAGE_ALIGN64(SIZE);
bad = (unsigned long long)PAGE_ALIGN(SIZE);
fprintf(stdout, "good = %llu, bad = %llu\n", good, bad);
return 0;
}
$ gcc -O2 -o 64-bit-page-align 64-bit-page-align.c
$ ./64-bit-page-align
good = 4294967296, bad = 0
^^^^^^^
On a x86_64, instead, both PAGE_ALIGN()s work as expected:
$ uname -m
x86_64
$ gcc -O2 -o 64-bit-page-align 64-bit-page-align.c
$ ./64-bit-page-align
good = 4294967296, bad = 4294967296
At least we could add something like:
#ifdef CONFIG_32BIT
#define PAGE_ALIGN64(addr) (((((addr)+PAGE_SIZE-1))>>PAGE_SHIFT)<<PAGE_SHIFT)
#else
#define PAGE_ALIGN64(addr) PAGE_ALIGN(addr)
#endif
But IMHO the single PAGE_ALIGN64() implementation is more clear.
-Andrea
--
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 prev parent reply other threads:[~2008-06-11 20:17 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 15:29 [-mm][PATCH 0/4] Add memrlimit controller (v5) Balbir Singh
2008-05-21 15:29 ` [-mm][PATCH 1/4] Add memrlimit controller documentation (v5) Balbir Singh
2008-05-22 4:16 ` Andrew Morton
2008-05-22 10:13 ` Balbir Singh
2008-05-21 15:29 ` [-mm][PATCH 2/4] Setup the memrlimit controller (v5) Balbir Singh
2008-05-22 4:18 ` Andrew Morton
2008-05-22 10:14 ` Balbir Singh
2008-06-11 17:10 ` Andrea Righi
2008-06-11 17:33 ` Balbir Singh
2008-06-11 18:48 ` Andrea Righi
2008-06-11 19:15 ` Andrew Morton
2008-06-11 20:17 ` Andrea Righi [this message]
2008-06-11 20:43 ` Andrew Morton
2008-06-11 22:47 ` Andrea Righi
2008-06-11 22:55 ` Andrew Morton
2008-06-11 23:04 ` Andrea Righi
2008-06-12 6:13 ` Balbir Singh
2008-06-12 8:52 ` Andrea Righi
2008-06-12 9:02 ` Andrew Morton
2008-06-12 9:12 ` Andrea Righi
2008-06-12 17:02 ` [PATCH -mm] PAGE_ALIGN(): correctly handle 64-bit values on 32-bit architectures Andrea Righi
2008-06-12 22:14 ` Andrea Righi
2008-06-13 9:37 ` Balbir Singh
2008-06-13 9:45 ` Li Zefan
2008-05-21 15:29 ` [-mm][PATCH 3/4] cgroup mm owner callback changes to add task info (v5) Balbir Singh
2008-05-22 4:19 ` Andrew Morton
2008-05-22 10:14 ` Balbir Singh
2008-05-21 15:30 ` [-mm][PATCH 4/4] Add memrlimit controller accounting and control (v5) Balbir Singh
2008-05-21 17:20 ` Vivek Goyal
2008-05-22 4:41 ` Balbir Singh
2008-05-22 4:24 ` Andrew Morton
2008-05-22 10:15 ` 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=485032C8.4010001@gmail.com \
--to=righi.andrea@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=skumar@linux.vnet.ibm.com \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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).