From: "Luck, Tony" <tony.luck@intel.com>
To: David Rientjes <rientjes@google.com>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"ebmunson@us.ibm.com" <ebmunson@us.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
"mtk.manpages@gmail.com" <mtk.manpages@gmail.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
"rth@twiddle.net" <rth@twiddle.net>,
"ink@jurassic.park.msu.ru" <ink@jurassic.park.msu.ru>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: RE: [PATCH] remove duplicate asm/mman.h files
Date: Mon, 21 Sep 2009 16:25:05 -0700 [thread overview]
Message-ID: <57C9024A16AD2D4C97DC78E552063EA3E29CC3F1@orsmsx505.amr.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0909211553000.30561@chino.kir.corp.google.com>
>> Is it perhaps the case that some UNIX on ia64 does implement MAP_GROWSUP,
>> and these numbers in the Linux ia64 mman.h have been chosen to match that
>> reference implementation? Tony will know. But I wonder if you'd do
>> better at least to leave a MAP_GROWSUP comment on that line, so that
>> somebody doesn't go and reuse the empty slot later on.
>>
>
> Reserving the bit from future use by adding a comment may be helpful, but
> then let's do it for MAP_GROWSDOWN too.
Tony can only speculate because this bit has been in asm/mman.h
since before I started working on Linux (it is in the 2.4.0
version ... which is roughly when I started ... and long before
I was responsible for it).
Perhaps it was assumed that it would be useful? Linux/ia64 does
use upwardly growing memory areas (the h/w register stack engine
saves "stack" registers to an area that grows upwards).
But since we have survived this long without it actually being
implemented, it may be true that we don't really need it after
all.
-Tony
--
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:[~2009-09-21 23:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 11:14 [PATCH 0/3] Add pseudo-anonymous huge page mappings V4 Eric B Munson
2009-08-25 11:14 ` [PATCH 1/3] hugetlbfs: Allow the creation of files suitable for MAP_PRIVATE on the vfs internal mount Eric B Munson
2009-08-25 11:14 ` [PATCH 2/3] Add MAP_HUGETLB for mmaping pseudo-anonymous huge page regions Eric B Munson
2009-08-25 11:14 ` [PATCH 3/3] Add MAP_HUGETLB example Eric B Munson
2009-09-17 22:44 ` [PATCH 2/3] Add MAP_HUGETLB for mmaping pseudo-anonymous huge page regions Andrew Morton
2009-09-18 0:46 ` Andrew Morton
2009-09-18 15:19 ` [PATCH] " Arnd Bergmann
2009-09-18 16:48 ` [PATCH] remove duplicate asm/mman.h files Arnd Bergmann
2009-09-18 19:37 ` David Rientjes
2009-09-21 8:31 ` Arnd Bergmann
2009-09-21 9:13 ` David Rientjes
2009-09-21 9:30 ` Arnd Bergmann
2009-09-21 12:02 ` Hugh Dickins
2009-09-21 22:55 ` David Rientjes
2009-09-21 23:25 ` Luck, Tony [this message]
2009-09-21 23:46 ` David Rientjes
2009-09-21 23:58 ` Ulrich Drepper
2009-09-21 12:27 ` Eric B Munson
2009-09-21 12:25 ` [PATCH] Add MAP_HUGETLB for mmaping pseudo-anonymous huge page regions Eric B Munson
2009-08-26 19:34 ` [PATCH 1/3] hugetlbfs: Allow the creation of files suitable for MAP_PRIVATE on the vfs internal mount David Rientjes
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=57C9024A16AD2D4C97DC78E552063EA3E29CC3F1@orsmsx505.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ebmunson@us.ibm.com \
--cc=fenghua.yu@intel.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=rientjes@google.com \
--cc=rth@twiddle.net \
/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