From: Mingming Cao <cmm@us.ibm.com>
To: tytso@mit.edu
Cc: john stultz <johnstul@us.ibm.com>,
linux-ext4@vger.kernel.org, keith maanthey <kmannth@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Darren Hart <dvhltc@us.ibm.com>
Subject: Re: ext4 dbench performance with CONFIG_PREEMPT_RT
Date: Thu, 08 Apr 2010 15:37:17 -0700 [thread overview]
Message-ID: <1270766237.2662.3.camel@mingming-laptop> (raw)
In-Reply-To: <20100408034631.GB23188@thunk.org>
On Wed, 2010-04-07 at 23:46 -0400, tytso@mit.edu wrote:
> On Wed, Apr 07, 2010 at 04:21:18PM -0700, john stultz wrote:
> > Further using lockstat I was able to isolate it the contention down to
> > the journal j_state_lock, and then adding some lock owner tracking, I
> > was able to see that the lock owners were almost always in
> > start_this_handle, and jbd2_journal_stop when we saw contention (with
> > the freq breakdown being about 55% in jbd2_journal_stop and 45% in
> > start_this_handle).
>
> Hmm.... I've taken a very close look at jbd2_journal_stop(), and I
> don't think we need to take j_state_lock() at all except if we need to
> call jbd2_log_start_commit(). t_outstanding_credits,
> h_buffer_credits, and t_updates are all documented (and verified by
> me) to be protected by the t_handle_lock spinlock.
>
Seems so, I verified the code, looks we could drop the j_state_lock()
there.
Also, I wonder if we could make the journal->j_average_commit_time as
atomic, so we could drop the j_state_lock() more in jbd2_journal_stop()?
Not sure how much this will improve the rt kernel, but might be worth
doing since j_state_lock() seems to be the hottest one.
Mingming
> So I ***think*** the following might be safe. WARNING! WARNING!! No
> real testing done on this patch, other than "it compiles! ship it!!".
>
> I'll let other people review it, and maybe you could give this a run
> and see what happens with this patch?
>
> - Ted
>
> diff --git a/fs/jbd2/transaction.c b/fs/jbd2/transaction.c
> index bfc70f5..e214d68 100644
> --- a/fs/jbd2/transaction.c
> +++ b/fs/jbd2/transaction.c
> @@ -1311,7 +1311,6 @@ int jbd2_journal_stop(handle_t *handle)
> if (handle->h_sync)
> transaction->t_synchronous_commit = 1;
> current->journal_info = NULL;
> - spin_lock(&journal->j_state_lock);
> spin_lock(&transaction->t_handle_lock);
> transaction->t_outstanding_credits -= handle->h_buffer_credits;
> transaction->t_updates--;
> @@ -1340,8 +1339,7 @@ int jbd2_journal_stop(handle_t *handle)
> jbd_debug(2, "transaction too old, requesting commit for "
> "handle %p\n", handle);
> /* This is non-blocking */
> - __jbd2_log_start_commit(journal, transaction->t_tid);
> - spin_unlock(&journal->j_state_lock);
> + jbd2_log_start_commit(journal, transaction->t_tid);
>
> /*
> * Special case: JBD2_SYNC synchronous updates require us
> @@ -1351,7 +1349,6 @@ int jbd2_journal_stop(handle_t *handle)
> err = jbd2_log_wait_commit(journal, tid);
> } else {
> spin_unlock(&transaction->t_handle_lock);
> - spin_unlock(&journal->j_state_lock);
> }
>
> lock_map_release(&handle->h_lockdep_map);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-08 22:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 23:21 ext4 dbench performance with CONFIG_PREEMPT_RT john stultz
2010-04-08 3:46 ` tytso
2010-04-08 10:18 ` Theodore Tso
2010-04-08 20:41 ` john stultz
2010-04-08 21:10 ` tytso
2010-04-13 3:52 ` john stultz
2010-04-14 3:04 ` john stultz
2010-04-08 22:37 ` Mingming Cao [this message]
2010-04-12 19:46 ` Jan Kara
2010-04-13 14:52 ` tytso
2010-04-13 16:25 ` Darren Hart
2010-06-02 22:35 ` j_state_lock patch data (was: Re: ext4 dbench performance with CONFIG_PREEMPT_RT) Eric Whitney
2010-04-09 15:49 ` ext4 dbench performance with CONFIG_PREEMPT_RT Andi Kleen
2010-04-09 23:33 ` tytso
2010-04-09 23:48 ` Chen, Tim C
2010-04-09 23:57 ` john stultz
2010-04-10 11:58 ` tytso
2010-04-12 19:54 ` Chen, Tim C
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=1270766237.2662.3.camel@mingming-laptop \
--to=cmm@us.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=kmannth@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.