From: "Chenjie (K)" <chenjie6@huawei.com>
To: catalin.marinas@arm.com, will.deacon@arm.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
panxuesong@huawei.com, caojiayin@huawei.com
Subject: arm: why set MIN_GAP to 128M size
Date: Mon, 7 Nov 2016 14:09:23 +0800 [thread overview]
Message-ID: <58201A93.70309@huawei.com> (raw)
Hi everyone
arm:
/* gap between mmap and stack */
#define MIN_GAP (128*1024*1024UL)
The min_gap is 128M,
in the mmap_base function
unsigned long gap = rlimit(RLIMIT_STACK);
if (gap < MIN_GAP)
gap = MIN_GAP;
else if (gap > MAX_GAP)
gap = MAX_GAP;
I can not use the "128-stack_size"(M)
can i modify it to 64M?
Thanks,
jie chen
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: "Chenjie (K)" <chenjie6@huawei.com>
To: <catalin.marinas@arm.com>, <will.deacon@arm.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<panxuesong@huawei.com>, <caojiayin@huawei.com>
Subject: arm: why set MIN_GAP to 128M size
Date: Mon, 7 Nov 2016 14:09:23 +0800 [thread overview]
Message-ID: <58201A93.70309@huawei.com> (raw)
Hi everyone
arm:
/* gap between mmap and stack */
#define MIN_GAP (128*1024*1024UL)
The min_gap is 128M,
in the mmap_base function
unsigned long gap = rlimit(RLIMIT_STACK);
if (gap < MIN_GAP)
gap = MIN_GAP;
else if (gap > MAX_GAP)
gap = MAX_GAP;
I can not use the "128-stack_size"(M)
can i modify it to 64M?
Thanks,
jie chen
next reply other threads:[~2016-11-07 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 6:09 Chenjie (K) [this message]
2016-11-07 6:09 ` arm: why set MIN_GAP to 128M size Chenjie (K)
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=58201A93.70309@huawei.com \
--to=chenjie6@huawei.com \
--cc=caojiayin@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=panxuesong@huawei.com \
--cc=will.deacon@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.