summaryrefslogtreecommitdiffstats
path: root/mm/kmemcheck.c
diff options
context:
space:
mode:
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-07-12 16:28:08 +0300
committerAl Viro <viro@zeniv.linux.org.uk>2012-07-22 23:58:16 +0400
commit9e9ad5f408889db6038a59b38ede29ff1ba9ef2f (patch)
tree1ceddb870378c5cd272959a54c18ed5909291d44 /mm/kmemcheck.c
parent7bd54ef722e9938768f524677be0ac4985d8473a (diff)
downloadop-kernel-dev-9e9ad5f408889db6038a59b38ede29ff1ba9ef2f.zip
op-kernel-dev-9e9ad5f408889db6038a59b38ede29ff1ba9ef2f.tar.gz
fs/ufs: get rid of write_super
This patch makes UFS stop using the VFS '->write_super()' method along with the 's_dirt' superblock flag, because they are on their way out. The way we implement this is that we schedule a delay job instead relying on 's_dirt' and '->write_super()'. The whole "superblock write-out" VFS infrastructure is served by the 'sync_supers()' kernel thread, which wakes up every 5 (by default) seconds and writes out all dirty superblocks using the '->write_super()' call-back. But the problem with this thread is that it wastes power by waking up the system every 5 seconds, even if there are no diry superblocks, or there are no client file-systems which would need this (e.g., btrfs does not use '->write_super()'). So we want to kill it completely and thus, we need to make file-systems to stop using the '->write_super()' VFS service, and then remove it together with the kernel thread. Tested using fsstress from the LTP project. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'mm/kmemcheck.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud