From: Alexandre Ghiti <aghiti@upmem.com>
To: palmer@sifive.com
Cc: aou@eecs.berkeley.edu, catalin.marinas@arm.com,
ndesaulniers@google.com, linux-riscv@lists.infradead.org,
Alexandre Ghiti <aghiti@upmem.com>,
atish.patra@wdc.com, akpm@linux-foundation.org, mingo@kernel.org,
mike.kravetz@oracle.com
Subject: [PATCH 3/3] riscv: Adjust mmap base address at a third of task size
Date: Mon, 10 Dec 2018 06:21:46 +0000 [thread overview]
Message-ID: <20181210062146.24951-4-aghiti@upmem.com> (raw)
In-Reply-To: <20181210062146.24951-1-aghiti@upmem.com>
This ratio is the most used among all other architectures and make
icache_hygiene libhugetlbfs test pass: this test mmap lots of
hugepages whose addresses, without this patch, reach the end of
the process user address space.
Signed-off-by: Alexandre Ghiti <aghiti@upmem.com>
---
arch/riscv/include/asm/processor.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/include/asm/processor.h b/arch/riscv/include/asm/processor.h
index 0531f49af5c3..ce70bceb8872 100644
--- a/arch/riscv/include/asm/processor.h
+++ b/arch/riscv/include/asm/processor.h
@@ -22,7 +22,7 @@
* This decides where the kernel will search for a free chunk of vm
* space during mmap's.
*/
-#define TASK_UNMAPPED_BASE PAGE_ALIGN(TASK_SIZE >> 1)
+#define TASK_UNMAPPED_BASE PAGE_ALIGN(TASK_SIZE / 3)
#define STACK_TOP TASK_SIZE
#define STACK_TOP_MAX STACK_TOP
--
2.16.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-12-10 6:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 6:21 [PATCH 0/3] Hugetlbfs support for riscv Alexandre Ghiti
2018-12-10 6:21 ` [PATCH 1/3] riscv: Introduce huge page support for 32/64bit kernel Alexandre Ghiti
2019-01-11 6:18 ` Paul Walmsley
2019-01-11 13:58 ` Alexandre Ghiti
2019-01-15 16:11 ` Christoph Hellwig
2019-01-15 18:52 ` Alex Ghiti
2018-12-10 6:21 ` [PATCH 2/3] riscv: Fix wrong comment about task size for riscv64 Alexandre Ghiti
2019-01-15 15:58 ` Christoph Hellwig
2019-01-15 18:53 ` Alex Ghiti
2019-02-07 12:52 ` Alexandre Ghiti
2018-12-10 6:21 ` Alexandre Ghiti [this message]
2019-01-15 16:02 ` [PATCH 3/3] riscv: Adjust mmap base address at a third of task size Christoph Hellwig
2019-01-15 18:54 ` Alex Ghiti
2019-01-25 19:02 ` Palmer Dabbelt
2019-01-26 9:23 ` Alex Ghiti
2019-01-27 16:57 ` Alex Ghiti
2019-01-28 11:17 ` Alexandre Ghiti
2019-01-07 17:57 ` [PATCH 0/3] Hugetlbfs support for riscv Alex Ghiti
2019-01-07 21:52 ` Paul Walmsley
2019-01-08 9:26 ` Alexandre Ghiti
2019-01-09 18:26 ` Palmer Dabbelt
2019-01-09 19:23 ` Mike Kravetz
2019-01-09 22:15 ` Palmer Dabbelt
2019-01-10 7:33 ` Alex Ghiti
2019-01-10 8:09 ` Alex Ghiti
2019-01-10 18:28 ` Mike Kravetz
2019-01-12 1:09 ` Alex Ghiti
2019-01-15 16:04 ` Christoph Hellwig
2019-01-15 18:56 ` Alex Ghiti
2019-01-15 19:25 ` Mike Kravetz
2019-01-15 20:52 ` Christoph Hellwig
2019-01-16 13:18 ` Alexandre Ghiti
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=20181210062146.24951-4-aghiti@upmem.com \
--to=aghiti@upmem.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=catalin.marinas@arm.com \
--cc=linux-riscv@lists.infradead.org \
--cc=mike.kravetz@oracle.com \
--cc=mingo@kernel.org \
--cc=ndesaulniers@google.com \
--cc=palmer@sifive.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 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).