From: Hugh Dickins <hugh@veritas.com>
To: Robin Holt <holt@sgi.com>
Cc: Dave Hansen <haveblue@us.ibm.com>, Greg KH <greg@kroah.com>,
ia64 list <linux-ia64@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
hch@infradead.org, jgarzik@pobox.com,
William Lee Irwin III <wli@holomorphy.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Carsten Otte <cotte@de.ibm.com>,
Jack Steiner <steiner@americas.sgi.com>
Subject: Re: [Patch 2/3] Export get_one_pte_map.
Date: Mon, 17 Oct 2005 13:33:53 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.61.0510171331090.2993@goblin.wat.veritas.com> (raw)
In-Reply-To: <20051017114730.GC30898@lnx-holt.americas.sgi.com>
On Mon, 17 Oct 2005, Robin Holt wrote:
> On Mon, Oct 17, 2005 at 01:41:52PM +0200, Dave Hansen wrote:
> > On Mon, 2005-10-17 at 06:31 -0500, Robin Holt wrote:
> > > On Fri, Oct 14, 2005 at 02:30:38PM -0700, Greg KH wrote:
> > > > On Fri, Oct 14, 2005 at 02:22:25PM -0500, Robin Holt wrote:
> > > > > +EXPORT_SYMBOL(get_one_pte_map);
>
> I got a little push from our internal incident tracking system for
> this being a module. _GPL it will be.
Sorry, Robin, I've not been following your patches. But if you look
at 2.6.14-rc4-mm1, you'll find that there isn't even a get_one_pte_map
there. Though there's no certainty yet that my pt locking changes, or
Nick's PageReserved changes, will actually go forward, there's a lot of
work queued up in -mm that is likely to affect your code. And I don't
think exporting internal functions from mremap.c, _GPL or otherwise,
is the way to go.
Moving useful functions to a more central location might be. But I'm
very dubious about your doing this kind of pte stuff deep down in an
architecture-specific driver. You're not the only one interested in
this kind of functionality: we were thinking of providing it via an
alternative to the ->nopage method, which deals in pfns rather than
struct pages (I think that was wli's suggestion originally; Carsten
has an interest in it on s390, and I bet there are others). There
may be excellent reasons why that wouldn't be good enough for you,
and your retcode method may be a better idea: I don't know yet.
Please rebase your work to 2.6.14-rc4-mm1 (but I won't get to look
at the result for a few days: perhaps others will).
The big question has to be: what are you expecting to happen for
PROT_WRITE, MAP_PRIVATE?
Hugh
--
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:[~2005-10-17 12:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 19:21 [Patch 0/3] SGI Altix and ia64 special memory support Robin Holt
2005-10-14 19:21 ` [Patch 1/3] Add a NOPAGE_FAULTED flag Robin Holt
2005-10-14 19:22 ` [Patch 2/3] Export get_one_pte_map Robin Holt
2005-10-14 21:30 ` Greg KH
2005-10-17 11:31 ` Robin Holt
2005-10-17 11:36 ` Christoph Hellwig
2005-10-17 11:39 ` Robin Holt
2005-10-17 11:41 ` Dave Hansen
2005-10-17 11:47 ` Robin Holt
2005-10-17 12:33 ` Hugh Dickins [this message]
2005-10-17 15:14 ` Robin Holt
2005-10-17 15:20 ` Greg KH
2005-10-17 15:56 ` Robin Holt
2005-10-17 16:05 ` Greg KH
2005-10-17 16:09 ` Dave Hansen
2005-10-17 16:14 ` Hugh Dickins
2005-10-17 20:53 ` Andrew Morton
2005-10-18 8:48 ` Carsten Otte
2005-10-17 15:59 ` Hugh Dickins
2005-10-17 20:25 ` Robin Holt
2005-10-17 20:59 ` Hugh Dickins
2005-10-18 23:28 ` William Lee Irwin III
2005-10-14 19:22 ` [Patch 3/3] Special Memory (mspec) driver Robin Holt
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=Pine.LNX.4.61.0510171331090.2993@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=cotte@de.ibm.com \
--cc=greg@kroah.com \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=holt@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=steiner@americas.sgi.com \
--cc=wli@holomorphy.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