> Unfortunately ext3 defeats the trick of setting the kupdate
> interval to something huge. On my list of things-to-do.
>
> Probably it's as simple as setting the commit timer to
> a large interval (grep for "HZ" in fs/jbd/journal.c).
How about using bdf_prm.b_un.interval as the commit
timer for ext3 ?
With the addition that normal writeouts to disk (those
go via the ext3 code, right?) also trigger a commit, if
the last commit was long enough ago to not impact system
efficiency.
This way you should, on laptops, have the ext3 commit
happening either at the same time as the kflushd write
(triggered by the write) or the next kflushd interval
away.
regards,
Rik
-- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)"
http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/