From: Peter Zijlstra <peterz@infradead.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC] mmaped copy too slow?
Date: Tue, 15 Jan 2008 10:08:27 +0100 [thread overview]
Message-ID: <1200388107.15103.23.camel@twins> (raw)
In-Reply-To: <20080115180130.119A.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Tue, 2008-01-15 at 18:03 +0900, KOSAKI Motohiro wrote:
> Hi Peter,
>
> > > > While being able to deal with used-once mappings in page reclaim
> > > > could be a good idea, this would require us to be able to determine
> > > > the difference between a page that was accessed once since it was
> > > > faulted in and a page that got accessed several times.
> > >
> > > it makes sense that read ahead hit assume used-once mapping, may be.
> > > I will try it.
> >
> > I once had a patch that made read-ahead give feedback into page reclaim,
> > but people didn't like it.
>
> Could you please tell me your mail subject or URL?
> I hope know why people didn't like.
I think this is the last thread on the subject:
http://lkml.org/lkml/2007/7/21/219
--
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:[~2008-01-15 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 1:45 KOSAKI Motohiro
2008-01-15 2:15 ` Rik van Riel
2008-01-15 3:20 ` KOSAKI Motohiro
2008-01-15 8:57 ` Peter Zijlstra
2008-01-15 9:03 ` KOSAKI Motohiro
2008-01-15 9:08 ` Peter Zijlstra [this message]
2008-01-15 12:46 ` Paulo Marques
2008-01-16 2:05 ` KOSAKI Motohiro
2008-01-17 3:23 ` KOSAKI Motohiro
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=1200388107.15103.23.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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