Jan Kara 3339578f05 jbd2: cleanup journal tail after transaction commit ... Normally, we have to issue a cache flush before we can update journal tail in journal superblock, effectively wiping out old transactions from the journal. So use the fact that during transaction commit we issue cache flush anyway and opportunistically push journal tail as far as we can. Since update of journal superblock is still costly (we have to use WRITE_FUA), we update log tail only if we can free significant amount of space. Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>		2012-03-13 22:45:38 -04:00
..
checkpoint.c	jbd2: remove bh_state lock from checkpointing code	2012-03-13 22:45:25 -04:00
commit.c	jbd2: cleanup journal tail after transaction commit	2012-03-13 22:45:38 -04:00
journal.c	jbd2: cleanup journal tail after transaction commit	2012-03-13 22:45:38 -04:00
Kconfig
Makefile
recovery.c	jbd2: issue cache flush after checkpointing even with internal journal	2012-03-13 22:22:54 -04:00
revoke.c	jbd2: use KMEM_CACHE instead of kmem_cache_create()	2012-02-20 17:53:03 -05:00
transaction.c	jbd2: remove always true condition in __journal_try_to_free_buffer()	2012-03-13 22:27:44 -04:00