From: Paul Mundt <lethal@linux-sh.org>
To: David Gibson <david@gibson.dropbear.id.au>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: Hugepage consolidation
Date: Mon, 2 May 2005 12:25:39 +0300 [thread overview]
Message-ID: <20050502092539.GA1766@linux-sh.org> (raw)
In-Reply-To: <20050502043035.GB12670@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
On Mon, May 02, 2005 at 02:30:35PM +1000, David Gibson wrote:
> - does SH4 need s special huge_ptep_get_and_clear()??
>
It does if we are trying to do multiple ptes per hugepage, but we can
actually drop most of that stuff (including ARCH_HAS_SETCLEAR_HUGE_PTE),
and use ptep_get_and_clear() instead.
We only actual have one pte per hugepage, having multiple ptes for the
page range at least for sh/sh64 was roughly an experiment in trying to
get larger ranges working, but this turned out not to be useful, so we
can pretty much switch to the more generic way of handling this.
I have patches that drop this behaviour already, so I'll bounce these
along to Andrew if this goes in -mm.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-05-02 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 4:30 Hugepage consolidation David Gibson
2005-05-02 9:25 ` Paul Mundt [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=20050502092539.GA1766@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@osdl.org \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.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