From: "girish" <girishc@india.hp.com>
To: <kapish@ureach.com>, "Bryan Henderson" <hbryan@us.ibm.com>
Cc: <linux-fsdevel@vger.kernel.org>
Subject: Re: Re: triggering do_writepages
Date: Wed, 20 Nov 2002 15:50:24 +0530 [thread overview]
Message-ID: <00cc01c2907e$722e6f40$9e744c0f@nt16158> (raw)
In-Reply-To: 200211200816.DAA16049@www22.ureach.com
> The situation being that I want to invoke
> some code in do_writepages path for a
> particular filesystem ( identified by the
> super_block, say ). In that case, when I
> issue writes on the filesystem, I do see the
> commit/prepare write path activated ASAP as
> it it should be. But on a explicit sync on
> the filesystem, I don't see writepages for
> that filesystem activated.
sys_sync->sync_fdev->sync_inodes>__sync_one->filemap_fdatasync->writepage if
"drty pages are avilable"
prev parent reply other threads:[~2002-11-20 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 8:16 Re: triggering do_writepages Kapish K
2002-11-20 10:20 ` girish [this message]
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='00cc01c2907e$722e6f40$9e744c0f@nt16158' \
--to=girishc@india.hp.com \
--cc=hbryan@us.ibm.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).