Searched hist:"9 fff24aa2c5c504aadead1ff9599e813604c2e53" (Results 1 – 3 of 3) sorted by relevance
| /linux/include/trace/events/ |
| H A D | jbd2.h | diff 9fff24aa2c5c504aadead1ff9599e813604c2e53 Thu Feb 07 04:30:23 CET 2013 Theodore Ts'o <tytso@mit.edu> 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>
|
| /linux/fs/jbd2/ |
| H A D | commit.c | diff 9fff24aa2c5c504aadead1ff9599e813604c2e53 Thu Feb 07 04:30:23 CET 2013 Theodore Ts'o <tytso@mit.edu> 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>
|
| H A D | transaction.c | diff 9fff24aa2c5c504aadead1ff9599e813604c2e53 Thu Feb 07 04:30:23 CET 2013 Theodore Ts'o <tytso@mit.edu> 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>
|