From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: benh@kernel.crashing.org
Cc: nai.xia@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, akpm@linux-foundation.org, hughd@google.com,
dave@linux.vnet.ibm.com, kamezawa.hiroyu@jp.fujitsu.com,
lethal@linux-sh.org, linux@arm.linux.org.uk
Subject: Re: mm: convert vma->vm_flags to 64bit
Date: Thu, 10 Nov 2011 16:49:49 -0500 [thread overview]
Message-ID: <4EBC46FD.5010109@jp.fujitsu.com> (raw)
In-Reply-To: <1320959579.21206.24.camel@pasglop>
On 11/10/2011 4:12 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2011-11-10 at 12:22 -0500, KOSAKI Motohiro wrote:
>> On 11/9/2011 11:09 PM, Nai Xia wrote:
>>> Hi all,
>>>
>>> Did this patch get merged at last, or on this way being merged, or
>>> just dropped ?
>>
>> Dropped.
>> Linus said he dislike 64bit enhancement.
>
> Do you have a pointer ? (And a rationale)
>
> I still want to put some arch flags in there at some point...
I'm sorry. I had got a machine crash awhile ago and I don't have
a past mail. If my remember is correctly, Linus said he worry about
an impact against 32bit x86 and he don't think current vm_flags
usage is enough efficient.
Maybe we need to ban useless arch specific flags at first.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-11-10 21:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 6:10 mm: convert vma->vm_flags to 64bit KOSAKI Motohiro
2011-04-12 6:33 ` Andrew Morton
2011-04-12 7:12 ` KOSAKI Motohiro
2011-04-12 11:06 ` Alexey Dobriyan
2011-04-12 11:11 ` Alexey Dobriyan
2011-04-12 22:07 ` Benjamin Herrenschmidt
2011-04-13 0:13 ` KOSAKI Motohiro
2011-04-13 6:44 ` Alexey Dobriyan
2011-04-13 7:00 ` Benjamin Herrenschmidt
2011-04-13 7:29 ` Russell King - ARM Linux
2011-04-13 8:56 ` Benjamin Herrenschmidt
2011-04-13 8:34 ` KOSAKI Motohiro
2011-04-13 7:04 ` KOSAKI Motohiro
2011-04-12 23:41 ` KOSAKI Motohiro
2011-04-13 2:19 ` [PATCH 1/3] mm: add __nocast attribute to vm_flags KOSAKI Motohiro
2011-04-13 2:20 ` [PATCH 2/3] fremap: convert vm_flags to unsigned long long KOSAKI Motohiro
2011-04-13 2:21 ` [PATCH 3/3] procfs: " KOSAKI Motohiro
2011-04-12 20:30 ` mm: convert vma->vm_flags to 64bit Russell King - ARM Linux
2011-04-18 0:26 ` Hugh Dickins
2011-04-18 1:21 ` KOSAKI Motohiro
2011-04-18 1:45 ` Benjamin Herrenschmidt
2011-04-18 3:34 ` KOSAKI Motohiro
2011-11-10 4:09 ` Nai Xia
2011-11-10 4:49 ` David Rientjes
2011-11-11 8:52 ` Russell King - ARM Linux
2011-11-10 17:22 ` KOSAKI Motohiro
2011-11-10 21:12 ` Benjamin Herrenschmidt
2011-11-10 21:49 ` KOSAKI Motohiro [this message]
2011-11-11 8:42 ` Russell King - ARM Linux
2011-11-11 2:09 ` Hugh Dickins
2011-11-11 4:31 ` Benjamin Herrenschmidt
2011-11-11 8:38 ` Nai Xia
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=4EBC46FD.5010109@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=nai.xia@gmail.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).