From: "Luck, Tony" <tony.luck@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Zhang Zhen <zhenzhang.zhang@huawei.com>
Cc: Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"james.hogan@imgtec.com" <james.hogan@imgtec.com>,
"ralf@linux-mips.org" <ralf@linux-mips.org>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"schwidefsky@de.ibm.com" <schwidefsky@de.ibm.com>,
"cmetcalf@ezchip.com" <cmetcalf@ezchip.com>,
David Rientjes <rientjes@google.com>,
"James.Yang@freescale.com" <James.Yang@freescale.com>,
"aneesh.kumar@linux.vnet.ibm.com"
<aneesh.kumar@linux.vnet.ibm.com>
Subject: RE: [PATCH] mm/hugetlb: reduce arch dependent code about huge_pmd_unshare
Date: Thu, 23 Apr 2015 22:26:18 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32A6478B@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <20150423151118.40c41fb1810f2aaa877163ae@linux-foundation.org>
> Memory fails me. Why do some architectures (arm, arm64, x86_64) want
> huge_pmd_[un]share() while other architectures (ia64, tile, mips,
> powerpc, metag, sh, s390) do not?
Potentially laziness/ignorance-of-feature? It looks like this feature started on x86_64 and then spread
to arm*.
Huge pages are weird on ia64 in that they have to be in a specific range of virtual addresses (region 4).
But I don't see why that would prevent sharing pmd's.
-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:[~2015-04-23 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1428996566-86763-1-git-send-email-zhenzhang.zhang@huawei.com>
2015-04-14 7:35 ` Zhang Zhen
2015-04-23 22:11 ` Andrew Morton
2015-04-23 22:26 ` Luck, Tony [this message]
2015-04-23 22:41 ` Andrew Morton
2015-04-24 15:46 ` Steve Capper
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=3908561D78D1C84285E8C5FCA982C28F32A6478B@ORSMSX114.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=James.Yang@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=cmetcalf@ezchip.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=ralf@linux-mips.org \
--cc=rientjes@google.com \
--cc=schwidefsky@de.ibm.com \
--cc=zhenzhang.zhang@huawei.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