From: Andrew Morton <akpm@linux-foundation.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Eli Cohen <eli@mellanox.co.il>, Roland Dreier <rdreier@cisco.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: FW: [PATCH] powerpc/mm: Export HPAGE_SHIFT
Date: Tue, 3 Feb 2009 21:13:29 -0800 [thread overview]
Message-ID: <20090203211329.d6190a08.akpm@linux-foundation.org> (raw)
In-Reply-To: <1233712248.16867.131.camel@pasglop>
On Wed, 04 Feb 2009 12:50:48 +1100 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> On Tue, 2009-02-03 at 17:08 -0800, Roland Dreier wrote:
> > Forwarding Eli's patch below, since PowerPC guys may have missed it. I
> > guess the question for Ben et al is whether there is any issue with
> > exporting HPAGE_SHIFT for modules (can be EXPORT_SYMBOL_GPL if you feel
> > it's an internal detail). It would probably make sense to roll this
> > change into the mlx4 change that Eli alludes to below and merge through
> > my tree (with ppc maintainer acks of course), rather than splitting this
> > patch out and introducing cross-tree dependencies (and also separating
> > the rationale for the change from the change itself).
> >
> > Thanks,
> > Roland
> >
> >
> > Drivers may want to take advantage of the large pages used for memory obtained
> > from hugetlbfs. One example is mlx4_ib which can use much less MTT entries (in
> > the order of HPAGE_SIZE / PAGE_SIZE) when registering such memory, thus scale
> > significantly better when registering larger memory regions. Other drivers
> > could also benefit from this.
>
> Except that we support multiple large page sizes nowadays ... I think
> the size can be specified per mountpoint of hugetlbfs no ? Thus things
> like mellanox would have to query the page size used for a given
> mapping.
>
> Do the generic hugetlbfs code provides such an API ? If not, we may need
> to add one.
>
I think it's something like
huge_page_size(page_hstate(page))
next prev parent reply other threads:[~2009-02-04 5:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090203164930.GA10101@mtls03>
2009-02-04 1:08 ` FW: [PATCH] powerpc/mm: Export HPAGE_SHIFT Roland Dreier
2009-02-04 1:50 ` Benjamin Herrenschmidt
2009-02-04 5:13 ` Andrew Morton [this message]
2009-02-04 5:31 ` Nick Piggin
2009-02-04 6:17 ` wli
2009-02-04 6:16 ` Roland Dreier
2009-02-04 6:26 ` Andrew Morton
2009-02-04 19:11 ` Roland Dreier
2009-02-04 21:00 ` wli
2009-02-04 21:31 ` Roland Dreier
2009-02-04 21:23 ` Andrew Morton
2009-02-04 23:55 ` Benjamin Herrenschmidt
2009-02-05 5:10 ` Roland Dreier
2009-02-05 5:24 ` Benjamin Herrenschmidt
2009-02-05 5:33 ` Roland Dreier
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=20090203211329.d6190a08.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=eli@mellanox.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rdreier@cisco.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).