diff options
author | Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | 2012-05-07 19:56:53 +0300 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2012-05-30 21:04:52 -0400 |
commit | 8bdc81c5069e43755d6e59e5e990e21ca200e8e2 (patch) | |
tree | eee9ff0210dcd0918a864b006feed14e5f715449 /mm/filemap.c | |
parent | 06688905cc36b86c700f376e9bc9bb68bc67d801 (diff) | |
download | linux-riscv-8bdc81c5069e43755d6e59e5e990e21ca200e8e2.tar.gz linux-riscv-8bdc81c5069e43755d6e59e5e990e21ca200e8e2.tar.bz2 linux-riscv-8bdc81c5069e43755d6e59e5e990e21ca200e8e2.zip |
jffs2: get rid of jffs2_sync_super
Currently JFFS2 file-system maps the VFS "superblock" abstraction to the
write-buffer. Namely, it uses VFS services to synchronize the write-buffer
periodically.
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 superblock 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 no matter what. 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.
This patch switches the JFFS2 write-buffer management from
'->write_super()'/'->s_dirt' to a delayed work. Instead of setting the 's_dirt'
flag we just schedule a delayed work for synchronizing the write-buffer.
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'mm/filemap.c')
0 files changed, 0 insertions, 0 deletions