jbd2-dont-unplog-after-revoke-records

   1 jbd2: don't unplug after writing revoke records
   2
   3 During commit process, keep the block device plugged after we are done
   4 writing the revoke records, until we are finished writing the rest of
   5 the commit records in the journal.  This will allow most of the
   6 journal blocks to be written in a single I/O operation, instead of
   7 separating the the revoke blocks from the rest of the journal blocks.
   8
   9 Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
  10 ---
  11  fs/jbd2/commit.c | 2 --
  12  1 file changed, 2 deletions(-)
  13
  14 diff --git a/fs/jbd2/commit.c b/fs/jbd2/commit.c
  15 index cf2fc05..765b31d 100644
  16 --- a/fs/jbd2/commit.c
  17 +++ b/fs/jbd2/commit.c
  18 @@ -555,7 +555,6 @@ void jbd2_journal_commit_transaction(journal_t *journal)
  19         blk_start_plug(&plug);
  20         jbd2_journal_write_revoke_records(journal, commit_transaction,
  21                                           &log_bufs, WRITE_SYNC);
  22 -       blk_finish_plug(&plug);
  23
  24         jbd_debug(3, "JBD2: commit phase 2b\n");
  25
  26 @@ -582,7 +581,6 @@ void jbd2_journal_commit_transaction(journal_t *journal)
  27         err = 0;
  28         bufs = 0;
  29         descriptor = NULL;
  30 -       blk_start_plug(&plug);
  31         while (commit_transaction->t_buffers) {
  32
  33                 /* Find the next buffer to be journaled... */