From: Andy Whitcroft <apw@shadowen.org>
To: akpm@osdl.org
Cc: apw@shadowen.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] topdown support for ppc64
Date: Wed, 01 Sep 2004 14:37:20 +0100 [thread overview]
Message-ID: <E1C2VIe-0005pb-P5@localhost.localdomain> (raw)
Recent patches introduced a top down user process address space
allocation policy; further patches enable this for ppc64.
Although these work correctly for normal maps, the topdown
algorithm does not take into account stringent mixing constraints
for small and large pages on this architecture. These patches
introduce a ppc64 specific arch_get_unused_area_topdown() variant.
The first introduces infrastructure to allow replacement of the
generic arch_get_unused_area_topdown() and the second utilises
this infrastructure.
In this patch I have followed the pattern set by the
arch_get_unused_area() using HAVE_ARCH_UNMAPPED_AREA_TOPDOWN to
be consistent. However, it would also be possible to simply have
a ppc64_get_unused_area_topdown() in the arch/ppc64/mm/mmap.c or
to use weak bindings.
-apw
=== 8< ===
Allow an architecture to override the default definition of
arch_get_unmapped_area_topdown().
Revision: $Rev: 602 $
Signed-off-by: Andy Whitcroft <apw@shadowen.org>
diffstat 090-arch_topdown
---
mmap.c | 2 ++
1 files changed, 2 insertions(+)
diff -X /home/apw/brief/lib/vdiff.excl -rupN reference/mm/mmap.c current/mm/mmap.c
--- reference/mm/mmap.c 2004-08-25 12:33:42.000000000 +0100
+++ current/mm/mmap.c 2004-08-26 12:26:59.000000000 +0100
@@ -1078,6 +1078,7 @@ void arch_unmap_area(struct vm_area_stru
* This mmap-allocator allocates new areas top-down from below the
* stack's low limit (the base):
*/
+#ifndef HAVE_ARCH_UNMAPPED_AREA_TOPDOWN
unsigned long
arch_get_unmapped_area_topdown(struct file *filp, const unsigned long addr0,
const unsigned long len, const unsigned long pgoff,
@@ -1162,6 +1163,7 @@ fail:
return addr;
}
+#endif
void arch_unmap_area_topdown(struct vm_area_struct *area)
{
reply other threads:[~2004-09-01 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1C2VIe-0005pb-P5@localhost.localdomain \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®