[PATCH 0/3] fs/sysv: stop using write_supers and s_dirt

From: Artem Bityutskiy
Date: Tue Jul 03 2012 - 09:42:36 EST

This patch-set makes sysv file-system stop using the VFS '->write_supers()'
call-back and the '->s_dirt' superblock field because I plan to remove them
once all users are gone.

Compile-tested only. If someone can give me a sysv image I could loop-mount
and test my changes - I'd appreciate. I could not find any tool to create this
ancient file-system. But I think my changes should not break it.


The goal is to get rid of the 'sync_supers()' kernel thread. This kernel thread
wakes up every 5 seconds (by default) and calls '->write_super()' for all
mounted file-systems. And the bad thing is that this is done even if all the
superblocks are clean. Moreover, many file-systems do not even need this end
they do not register the '->write_super()' method at all (e.g., btrfs).

So 'sync_supers()' most often just generates useless wake-ups and wastes power.
I am trying to make all file-systems independent of '->write_super()' and plan
to remove 'sync_supers()' and '->write_super()' completely once there are no
more users.

Overall status:

1. ext4: patches submitted,
2. exofs: patch submitted,
3. udf: patch submitted, sits in Jan Kara's tree:
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs for_testing
4. affs: patches submitted, sit in Al Viro's tree:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs for-next
5. hfs: patches submitted, sit Andrew Morton's tree
6. hfsplus: patches submitted, sit in Andre Morton's tree:
7. ext2: done, see commit f72cf5e223a28d3b3ea7dc9e40464fd534e359e8
8. vfat: done, see commit 78491189ddb6d84d4a4abae992ed891a236d0263
9. jffs2: done, see commit 208b14e507c00ff7f108e1a388dd3d8cc805a443
10. reiserfs: done, see commit 033369d1af1264abc23bea2e174aa47cdd212f6f

TODO: ufs

fs/sysv/inode.c | 18 +-----------------
fs/sysv/sysv.h | 1 -
2 files changed, 1 insertions(+), 18 deletions(-)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/