linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Daniel Phillips <daniel.phillips@innominate.de>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-mm@kvack.org
Subject: Re: Syncing the page cache, take 2
Date: Wed, 16 Aug 2000 21:49:29 +0100	[thread overview]
Message-ID: <20000816214929.F4037@redhat.com> (raw)
In-Reply-To: <news2mail-3999C0C9.301BB475@innominate.de>; from news-innominate.list.linux.mm@innominate.de on Wed, Aug 16, 2000 at 12:14:33AM +0200

Hi,

On Wed, Aug 16, 2000 at 12:14:33AM +0200, Daniel Phillips wrote:
> > 
> > (and even more ... we just about *need* the flush callback when
> > we're running in a multi-queue VM)
> 
> OK, but what about the case where the filesystem knows it wants the page
> cache to flush *right now*?  For example, when a filesystem wants to be
> sure the page cache is synced through to buffers just before marking a
> consistent state in the journal, say.  How does it make that happen?

Correct --- remember, Rik, that we talked about this?  It's not just
enough for the VM to call the address-space to flush dirty pages: you
also need to delegate the ability to manipulate the dirty status to
the fs.  In other words, you need a mark_page_dirty/clean() for pages
just as you already have for buffers.  

Do that and the filesystems can do pretty much what they want in
response to the callback.

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/

  parent reply	other threads:[~2000-08-16 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-15  8:32 Daniel Phillips
2000-08-15 18:46 ` Stephen C. Tweedie
2000-08-15 18:58   ` Rik van Riel
     [not found]     ` <news2mail-3999C0C9.301BB475@innominate.de>
2000-08-16 20:49       ` Stephen C. Tweedie [this message]
2000-08-16 21:06         ` Rik van Riel
     [not found] <3999C0C9.301BB475@innominate.de>
2000-08-15 22:21 ` 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=20000816214929.F4037@redhat.com \
    --to=sct@redhat.com \
    --cc=daniel.phillips@innominate.de \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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