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
..
acpi
asm-generic
crypto
drm
keys
linux	jbd2: cleanup journal tail after transaction commit	2012-03-13 22:45:38 -04:00
math-emu
media
misc
mtd
net
pcmcia
rdma
rxrpc
scsi
sound
target
trace	jbd2: issue cache flush after checkpointing even with internal journal	2012-03-13 22:22:54 -04:00
video
xen
Kbuild