From: "Stephen C. Tweedie" <sct@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
frankeh@us.ibm.com, Rik van Riel <riel@conectiva.com.br>,
Andreas Bombe <andreas.bombe@munich.netsurf.de>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: Best way to extend try_to_free_pages()?
Date: Wed, 17 May 2000 11:48:46 +0100 [thread overview]
Message-ID: <20000517114846.P30758@redhat.com> (raw)
In-Reply-To: <shsog65eck3.fsf@charged.uio.no>; from trond.myklebust@fys.uio.no on Wed, May 17, 2000 at 11:44:12AM +0200
Hi,
On Wed, May 17, 2000 at 11:44:12AM +0200, Trond Myklebust wrote:
>
> > The route we'll probably go for this is through
> > address_space_operations callbacks from shrink_mmap. That
> > allows proper fairness --- all fses can share the same lru that
> > way.
>
> Could such a proposal for a per-page flushing interface perhaps also
> be used for the implementation of more generic versions of 'sync()' &
> friends?
Right now, the write_super() callback to the fs is about the best
place to trap syncs. I'm not sure that you want to have per-page
callbacks for sync --- you really want the fs to be able to batch
things up itself.
Cheers,
Stephen
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-05-17 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-17 1:51 Best way to extend try_to_free_pages()? frankeh
2000-05-17 8:08 ` Stephen C. Tweedie
2000-05-17 9:44 ` Trond Myklebust
2000-05-17 10:48 ` Stephen C. Tweedie [this message]
[not found] <20000517005828.A3028@storm.local>
2000-05-16 23:46 ` Rik van Riel
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=20000517114846.P30758@redhat.com \
--to=sct@redhat.com \
--cc=andreas.bombe@munich.netsurf.de \
--cc=frankeh@us.ibm.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.