From: Nick Piggin <npiggin@suse.de>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
andi@firstfloor.org, apw@shadowen.org, jens.axboe@oracle.com,
mingo@elte.hu, pbadari@us.ibm.com, shaggy@austin.ibm.com,
tglx@linutronix.de, zach.brown@oracle.com
Subject: Re: + x86-implement-pte_special.patch added to -mm tree
Date: Wed, 4 Jun 2008 02:43:11 +0200 [thread overview]
Message-ID: <20080604004311.GA30863@wotan.suse.de> (raw)
In-Reply-To: <19f34abd0806030853p747c01bft7b773b21e1361bcb@mail.gmail.com>
On Tue, Jun 03, 2008 at 05:53:22PM +0200, Vegard Nossum wrote:
> On 6/3/08, akpm@linux-foundation.org <akpm@linux-foundation.org> wrote:
> >
> > The patch titled
> > x86: implement pte_special
> > has been added to the -mm tree. Its filename is
> > x86-implement-pte_special.patch
>
> ...
>
> > ------------------------------------------------------
> > Subject: x86: implement pte_special
> > From: Nick Piggin <npiggin@suse.de>
> >
> > Implement the pte_special bit for x86. This is required to support
> > lockless get_user_pages, because we need to know whether or not we can
> > refcount a particular page given only its pte (and no vma).
>
> Wait... what the heck is a "special" page? Isn't that a terrible name
> for _anything_? Or is there a tradition to the name? It sounds like it
> should be named "novma" or "autonomous" or something instead.
> Something that carries at least a little more information than
> "special". Where can I find the documentation for this bit?
It's the logical opposite of a "normal" page.
> Has this been discussed on LKML? Is the name a result of consensus or whim?
It has been posted many times.
prev parent reply other threads:[~2008-06-04 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806022356.m52NuRTj006330@imap1.linux-foundation.org>
2008-06-03 15:53 ` Vegard Nossum
2008-06-04 0:43 ` Nick Piggin [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=20080604004311.GA30863@wotan.suse.de \
--to=npiggin@suse.de \
--cc=andi@firstfloor.org \
--cc=apw@shadowen.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=shaggy@austin.ibm.com \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@gmail.com \
--cc=zach.brown@oracle.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
all inboxes | Powered by JetHome®