linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Martin Jambor <jamborm@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Writing out a (file) mmapped page
Date: Mon, 13 Jun 2005 10:32:50 +0800	[thread overview]
Message-ID: <2cd57c900506121932600e4db1@mail.gmail.com> (raw)
In-Reply-To: <8e70aacf050612094916d32276@mail.gmail.com>

On 6/13/05, Martin Jambor <jamborm@gmail.com> wrote:
> Hi,
> 
> I have spent a few hours trying to find out how dirty mmapped pages
> are written out in filesystems using the "generic" functions but so
> far I have not been successful. The main thing that escapes me is the
> following:
> 
> block_write_full_page() writes out only buffers marked dirty or whole
> page when there are no buffers associated with it. Where in kernel are
> buffers either marked dirty or stripped off a mmaped page when the
> page itself becomes dirty?  I would be very grateful for a pointer to
> the source, possibly accompanied by a brief explanation of how it gets
> called.
> 
> One comment in buffer.c suggests aops->prepare_write is called by a
> pagefault handler for mmaped pages but I found no such call (using
> cscope).

generic_file_buffered_write() calls a_ops->prepare_write().

-- 
Coywolf Qi Hunt
http://ahbl.org/~coywolf/

  reply	other threads:[~2005-06-13  2:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-12 16:49 Writing out a (file) mmapped page Martin Jambor
2005-06-13  2:32 ` Coywolf Qi Hunt [this message]
2005-06-13  6:57   ` Jörn Engel
2005-06-14 15:36 ` Anton Altaparmakov
2005-06-14 16:37   ` Nikita Danilov

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=2cd57c900506121932600e4db1@mail.gmail.com \
    --to=coywolf@gmail.com \
    --cc=jamborm@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).