From: Andrew Morton <akpm@linux-foundation.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Christoph Lameter <clameter@sgi.com>,
Nick Piggin <npiggin@suse.de>,
linux-kernel@vger.kernel.org, pj@sgi.com
Subject: Re: Pagecache: find_or_create_page does not call a proper page allocator function
Date: Tue, 24 Apr 2007 10:51:47 -0700 [thread overview]
Message-ID: <20070424105147.be823d3b.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0704241841190.19956@blonde.wat.veritas.com>
On Tue, 24 Apr 2007 18:45:03 +0100 (BST) Hugh Dickins <hugh@veritas.com> wrote:
> On Tue, 24 Apr 2007, Christoph Lameter wrote:
> > On Tue, 24 Apr 2007, Hugh Dickins wrote:
> >
> > > I've not yet looked at the patch under discussion, but this remark
> > > prompts me... a couple of days ago I got very worried by the various
> > > hard-wired GFP_HIGHUSER allocations in mm/migrate.c and mm/mempolicy.c,
> > > and wondered how those would work out if someone has a blockdev mmap'ed.
> >
> > Hmmm.... These not that critical given that 32 bit NUMA systems are a bit
> > rare.
>
> That's true. And everybody but the owners of those systems wish
> fervently that they didn't exist ;)
>
> > And if a page is in the wrong area then it can be bounced before I/O
> > is performed on it.
>
> I think that much is also true, but not where the problem lies.
> Isn't the problem that filesystems using these block devices
> expect their metadata to be accessible without kmap calls?
>
yup. wherever we dereference buffer_head.b_data we're touching
page_address(buffer_head.b_page) without kmapping.
next prev parent reply other threads:[~2007-04-24 17:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 21:11 Pagecache: find_or_create_page does not call a proper page allocator function Christoph Lameter
2007-04-23 21:29 ` Andrew Morton
2007-04-23 21:37 ` Christoph Lameter
2007-04-23 22:33 ` Christoph Lameter
2007-04-23 22:42 ` Christoph Lameter
2007-04-23 22:42 ` Andrew Morton
2007-04-24 13:09 ` Hugh Dickins
2007-04-24 17:11 ` Andrew Morton
2007-04-24 19:06 ` Hugh Dickins
2007-04-24 19:55 ` Christoph Lameter
2007-04-24 20:16 ` Hugh Dickins
2007-04-24 20:30 ` Christoph Lameter
2007-04-24 20:42 ` Andrew Morton
2007-04-24 20:44 ` Christoph Lameter
2007-04-24 20:53 ` Andrew Morton
2007-04-24 20:58 ` Christoph Lameter
2007-04-24 21:24 ` Andrew Morton
2007-04-24 21:28 ` Christoph Lameter
2007-04-24 17:38 ` Christoph Lameter
2007-04-24 17:45 ` Hugh Dickins
2007-04-24 17:48 ` Christoph Lameter
2007-04-24 17:51 ` Andrew Morton [this message]
2007-04-24 17:56 ` Christoph Lameter
2007-04-24 17:45 ` Christoph Lameter
2007-04-24 18:53 ` Hugh Dickins
2007-04-24 19:34 ` Christoph Lameter
2007-04-24 19:49 ` Andrew Morton
2007-04-24 19:59 ` Christoph Lameter
2007-04-24 20:10 ` Andrew Morton
2007-04-24 20:12 ` Christoph Lameter
2007-04-24 20:20 ` Andrew Morton
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=20070424105147.be823d3b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=pj@sgi.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