Theodore Ts'o 9fff24aa2c jbd2: track request delay statistics ... Track the delay between when we first request that the commit begin and when it actually begins, so we can see how much of a gap exists. In theory, this should just be the remaining scheduling quantuum of the thread which requested the commit (assuming it was not a synchronous operation which triggered the commit request) plus scheduling overhead; however, it's possible that real time processes might get in the way of letting the kjournald thread from executing. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>		2013-02-06 22:30:23 -05:00
..
checkpoint.c	jbd2: remove bh_state lock from checkpointing code	2012-03-13 22:45:25 -04:00
commit.c	jbd2: track request delay statistics	2013-02-06 22:30:23 -05:00
journal.c	jbd2: track request delay statistics	2013-02-06 22:30:23 -05:00
Kconfig	jbd2: Grab a reference to the crc32c driver if necessary	2012-05-27 07:50:56 -04:00
Makefile
recovery.c	jbd2: check return value of blkdev_issue_flush()	2012-08-17 09:56:17 -04:00
revoke.c	jbd2: checksum revocation blocks	2012-05-27 08:08:24 -04:00
transaction.c	jbd2: track request delay statistics	2013-02-06 22:30:23 -05:00