All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Steve French <smfltc@us.ibm.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: writethrough of mmapped pages
Date: Fri, 30 Jan 2004 16:02:18 -0800	[thread overview]
Message-ID: <20040130160218.5b485e44.akpm@osdl.org> (raw)
In-Reply-To: <1075505404.2322.9.camel@stevef95.austin.ibm.com>

Steve French <smfltc@us.ibm.com> wrote:
>
> Is there an easy way to locally force the page cache to do in effect
> writethrough of mmapped pages (when I lose my write caching token in
> cifs vfs e.g.)?  Standard writes can be hooked easily enough by wrapping
> the inode operation for write and only calling generic_write if they are
> (still) cacheable locally which is what I do in current code, but
> mmapped writes still go through the page cache presumably and thus would
> have to be synced if a non-mmmapped read followed an mmapped write of an
> overlapping range.

You mean that you want the filesytem to know whenever an application
attempts to modify a mmapped page?  After the modification, rather than
before?

Not sure how to do that - even if you modify the MM to take a trap on every
write the page still hasn't been modified on entry to the fault handler.


  reply	other threads:[~2004-01-31  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30 23:30 writethrough of mmapped pages Steve French
2004-01-31  0:02 ` Andrew Morton [this message]
2004-01-31 10:21   ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2004-01-31 23:15 Steve French
2004-01-31 23:45 ` Steve French
2004-02-01  0:16   ` Steve French

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=20040130160218.5b485e44.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=smfltc@us.ibm.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 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.