From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Adam Litke <agl@us.ibm.com>
Cc: Nick Piggin <npiggin@suse.de>,
akpm@linux-foundation.org, hugh@veritas.com,
Linux Memory Management <linux-mm@kvack.org>,
hch@infradead.org, "David C. Hansen [imap]" <haveblue@us.ibm.com>
Subject: Re: [RFC/PATCH] prepare_unmapped_area
Date: Wed, 07 Feb 2007 08:02:53 +1100 [thread overview]
Message-ID: <1170795774.2620.255.camel@localhost.localdomain> (raw)
In-Reply-To: <1170795164.26117.35.camel@localhost.localdomain>
> Yeah, you're right... Former revisions of the patch created a function
> called is_special_range() which for the moment only called
> is_hugepage_only_range(). The thought was that other types of "special
> ranges" could be checked for in this function. I guess that's basically
> the same idea as validate_area() below. That would work for me.
>
> > I was talking to hch and arjan yesterday on irc and we though about
> > having an mm hook validate_area() that could replace the
> > is_hugepage_only_range() hack and deal with my issue as well. As for
> > having prepare in the fops, do we need it at all if we call fops->g_u_a
> > in the MAP_FIXED case ?
>
> Nah, if we cleaned up g_u_a() so that it is always called, away goes the
> need for f_ops->prepare_unmapped_area().
Ok, I'll cook up a patch around those lines, possibly next week.
Ben.
--
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:[~2007-02-06 21:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200702060405.l1645R7G009668@shell0.pdx.osdl.net>
[not found] ` <1170736938.2620.213.camel@localhost.localdomain>
[not found] ` <20070206044516.GA16647@wotan.suse.de>
2007-02-06 5:04 ` [RFC/PATCH] prepare_unmapped_area Benjamin Herrenschmidt
2007-02-06 5:31 ` Andrew Morton
2007-02-06 5:46 ` Benjamin Herrenschmidt
2007-02-06 5:58 ` Andrew Morton
2007-02-06 6:02 ` Benjamin Herrenschmidt
2007-02-06 6:08 ` Andrew Morton
2007-02-06 6:12 ` Nick Piggin
2007-02-06 6:37 ` Andrew Morton
2007-02-06 6:40 ` Nick Piggin
2007-02-06 6:54 ` Andrew Morton
2007-02-06 9:55 ` Christoph Hellwig
2007-02-06 10:07 ` Benjamin Herrenschmidt
2007-02-06 10:23 ` Christoph Hellwig
2007-02-06 15:56 ` Adam Litke
2007-02-06 20:12 ` Benjamin Herrenschmidt
2007-02-06 20:52 ` Adam Litke
2007-02-06 21:02 ` Benjamin Herrenschmidt [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=1170795774.2620.255.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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).