linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andrea Righi <andrea@betterlinux.com>
Cc: "Minchan Kim" <minchan.kim@gmail.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
	"Andrea Arcangeli" <aarcange@redhat.com>,
	"Hugh Dickins" <hughd@google.com>,
	"Jerry James" <jamesjer@betterlinux.com>,
	"Marcus Sorensen" <marcus@bluehost.com>,
	"Matt Heaton" <matt@bluehost.com>,
	"KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>,
	"Rik van Riel" <riel@redhat.com>, "Theodore Tso" <tytso@mit.edu>,
	"Shaohua Li" <shaohua.li@intel.com>,
	"Pádraig Brady" <P@draigBrady.com>, linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] fadvise: move active pages to inactive list with POSIX_FADV_DONTNEED
Date: Tue, 28 Jun 2011 16:03:47 -0700	[thread overview]
Message-ID: <20110628160347.a5ffcc26.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110628225645.GB2274@thinkpad>

On Wed, 29 Jun 2011 00:56:45 +0200
Andrea Righi <andrea@betterlinux.com> wrote:

> > > 
> > > In this way if the backup was the only user of a page, that page will be
> > > immediately removed from the page cache by calling POSIX_FADV_DONTNEED.  If the
> > > page was also touched by other processes it'll be moved to the inactive list,
> > > having another chance of being re-added to the working set, or simply reclaimed
> > > when memory is needed.
> > 
> > So if an application touches a page twice and then runs
> > POSIX_FADV_DONTNEED, that page will now not be freed.
> > 
> > That's a big behaviour change.  For many existing users
> > POSIX_FADV_DONTNEED simply doesn't work any more!
> 
> Yes. This is the main concern that was raised by P__draig.
> 
> > 
> > I'd have thought that adding a new POSIX_FADV_ANDREA would be safer
> > than this.
> 
> Actually Jerry (in cc) proposed
> POSIX_FADV_IDONTNEEDTHISBUTIFSOMEBODYELSEDOESTHENDONTTOUCHIT in a
> private email. :)

Sounds good.  Needs more underscores though.

> > 
> > 
> > The various POSIX_FADV_foo's are so ill-defined that it was a mistake
> > to ever use them.  We should have done something overtly linux-specific
> > and given userspace more explicit and direct pagecache control.
> 
> That would give us the possibility to implement a wide range of
> different operations (drop, drop if used once, add to the active list,
> add to the inactive list, etc..). Some users always complain that they
> would like to have a better control over the page cache from userspace.

Well, I'd listen to proposals ;)

One thing we must be careful about is to not expose things like "active
list" to userspace.  linux-4.5 may not _have_ an active list, and its
implementors would hate us and would have to jump through hoops to
implement vaguely compatible behaviour in the new scheme.

So any primitives which are exposed should be easily implementable and
should *make sense* within any future scheme...

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-06-28 23:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 13:29 [PATCH v4 0/2] fadvise: move active pages to inactive list with POSIX_FADV_DONTNEED Andrea Righi
2011-06-27 13:29 ` [PATCH v4 1/2] mm: introduce __invalidate_mapping_pages() Andrea Righi
2011-06-27 13:29 ` [PATCH v4 2/2] fadvise: move active pages to inactive list with POSIX_FADV_DONTNEED Andrea Righi
2011-06-28 22:12 ` [PATCH v4 0/2] " Andrew Morton
2011-06-28 22:56   ` Andrea Righi
2011-06-28 23:03     ` Andrew Morton [this message]
2011-06-29 11:20       ` Pádraig Brady
2011-06-29 14:04         ` Andrea Righi

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=20110628160347.a5ffcc26.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=P@draigBrady.com \
    --cc=aarcange@redhat.com \
    --cc=andrea@betterlinux.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=jamesjer@betterlinux.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcus@bluehost.com \
    --cc=matt@bluehost.com \
    --cc=minchan.kim@gmail.com \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=shaohua.li@intel.com \
    --cc=tytso@mit.edu \
    /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).