From: Alex Tomas <alex@clusterfs.com>
To: linux-kernel@vger.kernel.org
Cc: ext2-devel@lists.sourceforge.net, akpm@osdl.org, alex@clusterfs.com
Subject: [PATCH] JBD: log space management optimization
Date: Wed, 19 Jan 2005 18:32:16 +0300 [thread overview]
Message-ID: <m3llapv3i7.fsf@bzzz.home.net> (raw)
Good day,
during truncate ext3 calls journal_forget() for freed blocks, but
before these blocks go to the transaction and jbd reserves space
in log for them (->t_outstanding_credits). also, journal_forget()
removes these blocks from the transaction, but doesn't correct
log space reservation. for example, removal of 500MB file reserves
136 blocks, but only 10 blocks go to the log. a commit is expensive
and correct reservation allows us to avoid needless commits. here
is the patch. tested on UP.
thanks, Alex
Signed-off-by: Alex Tomas <alex@clusterfs.com>
Index: linux-2.6.7/fs/jbd/transaction.c
===================================================================
--- linux-2.6.7.orig/fs/jbd/transaction.c 2004-08-26 17:12:40.000000000 +0400
+++ linux-2.6.7/fs/jbd/transaction.c 2005-01-19 17:23:30.058160408 +0300
@@ -1204,6 +1257,7 @@
transaction_t *transaction = handle->h_transaction;
journal_t *journal = transaction->t_journal;
struct journal_head *jh;
+ int drop_reserve = 0;
BUFFER_TRACE(bh, "entry");
@@ -1227,6 +1281,7 @@
J_ASSERT_JH(jh, !jh->b_committed_data);
__journal_unfile_buffer(jh);
+ drop_reserve = 1;
/*
* We are no longer going to journal this buffer.
@@ -1249,7 +1304,7 @@
spin_unlock(&journal->j_list_lock);
jbd_unlock_bh_state(bh);
__bforget(bh);
- return;
+ goto drop;
}
}
} else if (jh->b_transaction) {
@@ -1264,6 +1319,7 @@
if (jh->b_next_transaction) {
J_ASSERT(jh->b_next_transaction == transaction);
jh->b_next_transaction = NULL;
+ drop_reserve = 1;
}
}
@@ -1271,6 +1327,15 @@
spin_unlock(&journal->j_list_lock);
jbd_unlock_bh_state(bh);
__brelse(bh);
+
+drop:
+ if (drop_reserve) {
+ /* no need to reserve log space for this block -bzzz */
+ spin_lock(&transaction->t_handle_lock);
+ transaction->t_outstanding_credits--;
+ spin_unlock(&transaction->t_handle_lock);
+ }
+
return;
}
next reply other threads:[~2005-01-19 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 15:32 Alex Tomas [this message]
2005-01-24 18:56 ` [Ext2-devel] " Stephen C. Tweedie
2005-01-24 20:22 ` Alex Tomas
2005-01-24 20:58 ` Stephen C. Tweedie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3llapv3i7.fsf@bzzz.home.net \
--to=alex@clusterfs.com \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®