From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-fsdevel@vger.kernel.org
Subject: Handling sync system calls
Date: Wed, 10 May 2006 23:25:43 +1200 [thread overview]
Message-ID: <200605102325.43775.manningc2@actrix.gen.nz> (raw)
Hi all
I have written a so-called "cechkpointing" mechanism for the YAFFS2 file
system that stores a snapshot of the fs structure in some spare flash. When
the filesystem gets remounted, this info replaces the normal scanning process
and thus significantly speeds up mounting.
At this stage I have managed to attach the "checkpoint" writting to put_super
so that the info is stored during a umount, but have had some problems trying
to do the same with getting this to work with a sync call.
I don't really want the checkpoint data to get written too often as this will
slow down the fs and cause extra flashh wear. I really only want it to happen
as part of an explicite sync().
I tried attaching the checkpointing to the write_super() and sync_fs()
methods, but these either caused writing more often than I needed, or nothing
happened because sb->s_dirt was not set.
As a final twist it would be really handy for the solution to work with both
2.4 and 2.6 kernels. A lot of embedded systems still run 2.4.x.
ANy pointers on how to proceed much appreciated.
Thanx
-- Charles
reply other threads:[~2006-05-10 11:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200605102325.43775.manningc2@actrix.gen.nz \
--to=manningc2@actrix.gen.nz \
--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).