From: Catalin Marinas <catalin.marinas@arm.com>
To: David Rientjes <rientjes@google.com>
Cc: Steve Capper <steve.capper@linaro.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
Michal Hocko <mhocko@suse.cz>, Ken Chen <kenchen@google.com>,
Mel Gorman <mgorman@suse.de>, Will Deacon <Will.Deacon@arm.com>
Subject: Re: [RFC PATCH 0/2] mm: Promote huge_pmd_share from x86 to mm.
Date: Mon, 29 Apr 2013 23:10:35 +0100 [thread overview]
Message-ID: <20130429221034.GA49470@MacBook-Pro.local> (raw)
In-Reply-To: <alpine.DEB.2.02.1304291321070.29766@chino.kir.corp.google.com>
On Mon, Apr 29, 2013 at 09:22:38PM +0100, David Rientjes wrote:
> On Mon, 29 Apr 2013, Steve Capper wrote:
>
> > Under x86, multiple puds can be made to reference the same bank of
> > huge pmds provided that they represent a full PUD_SIZE of shared
> > huge memory that is aligned to a PUD_SIZE boundary.
> >
> > The code to share pmds does not require any architecture specific
> > knowledge other than the fact that pmds can be indexed, thus can
> > be beneficial to some other architectures.
> >
> > This RFC promotes the huge_pmd_share code (and dependencies) from
> > x86 to mm to make it accessible to other architectures.
> >
> > I am working on ARM64 support for huge pages and rather than
> > duplicate the x86 huge_pmd_share code, I thought it would be better
> > to promote it to mm.
>
> No objections to this, but I think you should do it as the first patch in
> a series that adds the arm support. There's no need for this to be moved
> until that support is tested, proposed, reviewed, and merged.
I agree, it would be good to see the arm64 support in this series as
well (though eventual upstreaming may go via separate paths).
--
Catalin
--
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>
prev parent reply other threads:[~2013-04-29 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 14:55 [RFC PATCH 0/2] mm: Promote huge_pmd_share from x86 to mm Steve Capper
2013-04-29 14:55 ` [RFC PATCH 1/2] mm: hugetlb: Copy " Steve Capper
2013-04-29 15:26 ` Catalin Marinas
2013-04-29 15:47 ` Steve Capper
2013-04-29 16:07 ` Catalin Marinas
2013-04-29 14:55 ` [RFC PATCH 2/2] x86: mm: Remove x86 version of huge_pmd_share Steve Capper
2013-04-29 20:22 ` [RFC PATCH 0/2] mm: Promote huge_pmd_share from x86 to mm David Rientjes
2013-04-29 22:10 ` Catalin Marinas [this message]
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=20130429221034.GA49470@MacBook-Pro.local \
--to=catalin.marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=kenchen@google.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=rientjes@google.com \
--cc=steve.capper@linaro.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).