linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: Kapish K <kapish@ureach.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: triggering do_writepages
Date: Wed, 20 Nov 2002 14:38:50 +0100	[thread overview]
Message-ID: <20021120133850.GA579@vagabond> (raw)
In-Reply-To: <200211190659.BAA00740@www23.ureach.com>

On Tue, Nov 19, 2002 at 01:59:33AM -0500, Kapish K wrote:
> 
> Hello,
>   I have a ( possibly simple ) question on
> how to trigger a do-writepages to get
> called, for a particular filesystem, on
> which I am issuing write calls. Any code
> that I put into the generic_file_write code
> ( around prepare_write or commit_write )
> gets triggered when a write is issues, but I
> don't seem to be getting do_writepages
> invoked for that filesystem ( when I check
> the sb pointer for my particular filesystem ). 
> Am I missing something basic in here?
> Any pointers will be most helpful
> Thanks in advance

... i can't find any do_writepages symbol...
Anyway, what is supposed to happen is, that in commit write you either
start the IO (and thus the write is done), or you mark the page dirty
(using set_page_dirty). Later, either when kernel needs to reuse the
page (during memory allocation), or when it decides the page is dirty
too long (in kflushd), it calls the writepage address_space method on
the page. This method must then start the IO (and setup a callback to
unlock it when IO completes and finish). If the IO completes OK, the
callback should set the page clean again so kernel can reuse it.

-------------------------------------------------------------------------------
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

  parent reply	other threads:[~2002-11-20 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19  6:59 triggering do_writepages Kapish K
2002-11-19 11:11 ` girish
2002-11-20 13:38 ` Jan Hudec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 18:27 Bryan Henderson

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=20021120133850.GA579@vagabond \
    --to=bulb@ucw.cz \
    --cc=kapish@ureach.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).