linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Chris Mason <mason@suse.com>
Cc: "Quintela Carreira Juan J." <quintela@fi.udc.es>,
	sct@redhat.com, linux-kernel@vger.rutgers.edu,
	linux-mm@kvack.org,
	"reiserfs@devlinux.com" <reiserfs@devlinux.com>
Subject: Re: memory pressure callbacks (was: 2.5 TODO)
Date: Tue, 6 Jun 2000 21:12:32 +0100	[thread overview]
Message-ID: <20000606211232.U23701@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10006061232040.9710-100000@home.suse.com>; from mason@suse.com on Tue, Jun 06, 2000 at 01:06:00PM -0700

Hi,

On Tue, Jun 06, 2000 at 01:06:00PM -0700, Chris Mason wrote:
> > 
> > Chris, I think that you don't want to put that in the address space
> > operations, the main reason is that you don't want your pages to stay
> > in the main LRU queue, because you need to freed them in an specific
> > order (not LRU at all).  Then if shrink_mmap is not scanning your
> > pages, it is better to use your own reclaim function, that would be
> > called from do_try_to_free_pages (a la shrink_[di]cache way).
> 
> The goal isn't to make something perfect for the journaled filesystems, it
> is a generic facility that also happens to work for the journaled
> filesystems.  So, I like the address space operations, mostly
> because this is an operation on an address space ;-)

Right.  There's one other major problem with a lot of page reclaim 
algorithms --- the algorithm can be the best in the world, but it needs
to be balanced against the other page stealers in the kernel too. 
Using the main LRUs for all filesystems, with address_space callbacks
to free pages, should make such balancing a lot easier to achieve.

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/

           reply	other threads:[~2000-06-06 20:12 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.LNX.4.10.10006061232040.9710-100000@home.suse.com>]

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=20000606211232.U23701@redhat.com \
    --to=sct@redhat.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=mason@suse.com \
    --cc=quintela@fi.udc.es \
    --cc=reiserfs@devlinux.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