From: Peter Zijlstra <peterz@infradead.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Hugh Dickins <hugh@veritas.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Nick Piggin <npiggin@suse.de>,
riel <riel@redhat.com>, Lennart Poettering <mztabzr@0pointer.de>
Subject: Re: [rfc][patch] mm: madvise(WILLNEED) for anonymous memory
Date: Thu, 20 Dec 2007 18:15:59 +0100 [thread overview]
Message-ID: <1198170959.30889.0.camel@lappy> (raw)
In-Reply-To: <20071220171143.GV19691@waste.org>
On Thu, 2007-12-20 at 11:11 -0600, Matt Mackall wrote:
> On Thu, Dec 20, 2007 at 05:53:41PM +0100, Peter Zijlstra wrote:
> >
> > On Thu, 2007-12-20 at 15:26 +0000, Hugh Dickins wrote:
> >
> > > The asynch code: perhaps not worth doing for MADV_WILLNEED alone,
> > > but might prove useful for more general use when swapping in.
> > > Not really the same as Con's swap prefetch, but worth looking
> > > at that for reference. But I guess this becomes a much bigger
> > > issue than you were intending to get into here.
> >
> > heh, yeah, got somewhat more complex that I'd hoped for.
> >
> > last patch for today (not even compile tested), will do a proper patch
> > and test it tomorrow.
> >
> > ---
> > A best effort MADV_WILLNEED implementation for anonymous memory.
> >
> > It adds a batch method to the page table walk routines so we can
> > copy a few ptes while holding the kmap, which makes it possible to
> > allocate the backing pages using GFP_KERNEL.
>
> Yuck. We actually need to just fix the atomic kmap issue in the
> existing pagemap code rather than add a new method, I think.
>
> If performance of map/unmap is too slow at a granularity of 1, we can
> add some internal batching in the CONFIG_HIGHPTE case.
OK, sounds like a much better idea indeed. Will implement that.
--
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:[~2007-12-20 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 13:05 Peter Zijlstra
2007-12-20 14:09 ` Hugh Dickins
2007-12-20 14:47 ` Peter Zijlstra
2007-12-20 14:56 ` Peter Zijlstra
2007-12-20 15:18 ` Peter Zijlstra
2007-12-20 15:23 ` Peter Zijlstra
2007-12-20 15:26 ` Hugh Dickins
2007-12-20 16:53 ` Peter Zijlstra
2007-12-20 17:11 ` Matt Mackall
2007-12-20 17:15 ` Peter Zijlstra [this message]
2007-12-20 16:29 ` Lennart Poettering
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=1198170959.30889.0.camel@lappy \
--to=peterz@infradead.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=mztabzr@0pointer.de \
--cc=npiggin@suse.de \
--cc=riel@redhat.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