From: Chris Wedgwood <cw@f00f.org>
To: Anton Blanchard <anton@samba.org>
Cc: akpm@osdl.org, nickpiggin@yahoo.com.au,
linux-kernel@vger.kernel.org, spyro@f2s.com
Subject: Re: [PATCH] Use MM_VM_SIZE in exit_mmap
Date: Tue, 25 Jan 2005 08:46:42 -0800 [thread overview]
Message-ID: <20050125164642.GA17927@taniwha.stupidest.org> (raw)
In-Reply-To: <20050125142210.GI5920@krispykreme.ozlabs.ibm.com>
On Wed, Jan 26, 2005 at 01:22:10AM +1100, Anton Blanchard wrote:
> The 4 level pagetable code changed the exit_mmap code to rely on
> TASK_SIZE. On some architectures (eg ppc64 and ia64), this is a per
> task property and bad things can happen in certain circumstances
> when using it.
I don't really like it in general when we do
#define MAYBE_CONST_LOOKING_THING (some_func())
I would almost rather see something like task_size(current) used.
> MM_VM_SIZE() was created for this purpose (and is used in the next
> line for tlb_finish_mmu), so use it. I moved the PGD round up of
> TASK_SIZE into the default MM_VM_SIZE.
> ===== include/linux/mm.h 1.212 vs edited =====
> +++ edited/include/linux/mm.h 2005-01-26 01:20:12 +11:00
> @@ -38,7 +38,7 @@
> #include <asm/atomic.h>
>
> #ifndef MM_VM_SIZE
> -#define MM_VM_SIZE(mm) TASK_SIZE
> +#define MM_VM_SIZE(mm) ((TASK_SIZE + PGDIR_SIZE - 1) & PGDIR_MASK)
> #endif
>
> #define nth_page(page,n) pfn_to_page(page_to_pfn((page)) + (n))
ia64 asm/processor.h already has:
#define DEFAULT_TASK_SIZE __IA64_UL_CONST(0xa000000000000000)
[...]
#define MM_VM_SIZE(mm) DEFAULT_TASK_SIZE
So I think this will generate a warning there?
next prev parent reply other threads:[~2005-01-25 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 14:22 Anton Blanchard
2005-01-25 16:46 ` Chris Wedgwood [this message]
2005-01-25 16:57 ` Anton Blanchard
2005-01-25 17:13 ` Chris Wedgwood
2005-01-27 20:46 ` [PATCH RFC] Change (some) TASK_SIZE to task_vtop(current) Chris Wedgwood
2005-01-25 23:02 ` [PATCH] Use MM_VM_SIZE in exit_mmap Ian Molton
2005-01-25 23:39 ` Russell King
2005-01-26 0:01 ` Anton Blanchard
2005-01-26 0:17 ` Nick Piggin
2005-01-26 6:44 ` Andi Kleen
2005-01-26 7:39 ` William Lee Irwin III
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=20050125164642.GA17927@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=spyro@f2s.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
all inboxes | Powered by JetHome®