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>
Showing
- fs/jbd2/commit.c 8 additions, 0 deletionsfs/jbd2/commit.c
- fs/jbd2/journal.c 9 additions, 3 deletionsfs/jbd2/journal.c
- fs/jbd2/transaction.c 1 addition, 0 deletionsfs/jbd2/transaction.c
- include/linux/jbd2.h 7 additions, 0 deletionsinclude/linux/jbd2.h
- include/trace/events/jbd2.h 6 additions, 2 deletionsinclude/trace/events/jbd2.h
Loading
Please register or sign in to comment