Re: Best way to extend try_to_free_pages()?

[Trond Myklebust <trond.myklebust@fys.uio.no>]

>>>>> " " == Stephen C Tweedie <sct@redhat.com> writes:

     > Chris Mason and I have already been looking at doing something
     > similar, but on a per-page basis, to allow advanced filesystems
     > to release memory in a controlled manner.  This is particularly
     > necessary for journaled filesystems, in which releasing certain
     > data may require a transaction commit --- until the commit,
     > there is just no way shrink_mmap() will be able to free those
     > pages, so there has to be a way for shrink_mmap() to let the
     > filesystem know that it wants some memory back.

     > 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?

Cheers,
  Trond
--
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/