linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "girish" <girishc@india.hp.com>
To: <kapish@ureach.com>
Cc: <linux-fsdevel@vger.kernel.org>
Subject: Re: triggering do_writepages
Date: Tue, 19 Nov 2002 16:41:26 +0530	[thread overview]
Message-ID: <006901c28fbc$678331b0$9e744c0f@nt16158> (raw)
In-Reply-To: 200211190659.BAA00740@www23.ureach.com

Hi,
  writepage is used when ever there is pressure for memory from VM system
and for mmaped files. I guess  writepage need not be triggered explictly. If
you want to add a functionaly for a writepage you can stack it at writepage,
which will be called implicitly


----- Original Message -----
From: "Kapish K" <kapish@ureach.com>
To: <linux-fsdevel@vger.kernel.org>
Sent: Tuesday, November 19, 2002 12:29 PM
Subject: triggering do_writepages


>
> 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
>
> ________________________________________________
> Get your own "800" number
> Voicemail, fax, email, and a lot more
> http://www.ureach.com/reg/tag
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel"
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2002-11-19 11:11 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 [this message]
2002-11-20 13:38 ` Jan Hudec
  -- 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='006901c28fbc$678331b0$9e744c0f@nt16158' \
    --to=girishc@india.hp.com \
    --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).