From: Joel Becker <Joel.Becker@oracle.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
ocfs2-devel@oss.oracle.com, Keith Maanthey <kmannth@us.ibm.com>,
John Stultz <johnstul@us.ibm.com>,
Eric Whitney <eric.whitney@hp.com>
Subject: Re: [Ocfs2-devel] [PATCH -v2 0/3] jbd2 scalability patches
Date: Mon, 9 Aug 2010 09:06:55 -0700 [thread overview]
Message-ID: <20100809160652.GA4743@mail.oracle.com> (raw)
In-Reply-To: <1280939957-3277-1-git-send-email-tytso@mit.edu>
On Wed, Aug 04, 2010 at 12:39:14PM -0400, Theodore Ts'o wrote:
> This version fixes three bugs in the 2nd patch of this series that
> caused kernel BUG when the system was under race. We weren't accounting
> with t_oustanding_credits correctly, and there were race conditions
> caused by the fact the I had overlooked the fact that
> __jbd2_log_wait_for_space() and jbd2_get_transaction() requires
> j_state_lock to be write locked.
>
Here's an initial set of runs. Not the fastest disk ever, but it shows
the patches don't hurt us.
http://oss.oracle.com/~mmatsuna/ocfs2-test/FFSB/FFSB.html
Joel
--
"I inject pure kryptonite into my brain.
It improves my kung fu, and it eases the pain."
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
WARNING: multiple messages have this Message-ID (diff)
From: Joel Becker <Joel.Becker@oracle.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
ocfs2-devel@oss.oracle.com, Keith Maanthey <kmannth@us.ibm.com>,
John Stultz <johnstul@us.ibm.com>,
Eric Whitney <eric.whitney@hp.com>
Subject: [Ocfs2-devel] [PATCH -v2 0/3] jbd2 scalability patches
Date: Mon, 9 Aug 2010 09:06:55 -0700 [thread overview]
Message-ID: <20100809160652.GA4743@mail.oracle.com> (raw)
In-Reply-To: <1280939957-3277-1-git-send-email-tytso@mit.edu>
On Wed, Aug 04, 2010 at 12:39:14PM -0400, Theodore Ts'o wrote:
> This version fixes three bugs in the 2nd patch of this series that
> caused kernel BUG when the system was under race. We weren't accounting
> with t_oustanding_credits correctly, and there were race conditions
> caused by the fact the I had overlooked the fact that
> __jbd2_log_wait_for_space() and jbd2_get_transaction() requires
> j_state_lock to be write locked.
>
Here's an initial set of runs. Not the fastest disk ever, but it shows
the patches don't hurt us.
http://oss.oracle.com/~mmatsuna/ocfs2-test/FFSB/FFSB.html
Joel
--
"I inject pure kryptonite into my brain.
It improves my kung fu, and it eases the pain."
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-08-09 16:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 16:39 [PATCH -v2 0/3] jbd2 scalability patches Theodore Ts'o
2010-08-04 16:39 ` [Ocfs2-devel] " Theodore Ts'o
2010-08-04 16:39 ` [PATCH -v2 1/3] jbd2: Use atomic variables to avoid taking t_handle_lock in jbd2_journal_stop Theodore Ts'o
2010-08-04 16:39 ` [Ocfs2-devel] " Theodore Ts'o
2010-08-09 17:02 ` Jan Kara
2010-08-09 17:02 ` [Ocfs2-devel] " Jan Kara
2010-08-09 19:05 ` Ted Ts'o
2010-08-09 19:05 ` [Ocfs2-devel] " Ted Ts'o
2010-08-09 19:45 ` Jan Kara
2010-08-09 19:45 ` [Ocfs2-devel] " Jan Kara
2010-08-10 16:30 ` Ted Ts'o
2010-08-10 16:30 ` [Ocfs2-devel] " Ted Ts'o
2010-08-11 22:16 ` Jan Kara
2010-08-11 22:16 ` [Ocfs2-devel] " Jan Kara
2010-08-04 16:39 ` [PATCH -v2 2/3] jbd2: Change j_state_lock to be a rwlock_t Theodore Ts'o
2010-08-04 16:39 ` [Ocfs2-devel] " Theodore Ts'o
2010-08-04 16:39 ` [PATCH -v2 3/3] jbd2: Remove t_handle_lock from start_this_handle() Theodore Ts'o
2010-08-04 16:39 ` [Ocfs2-devel] " Theodore Ts'o
2010-08-05 1:58 ` [PATCH -v2 0/3] jbd2 scalability patches john stultz
2010-08-05 1:58 ` [Ocfs2-devel] " john stultz
2010-08-05 5:42 ` Ted Ts'o
2010-08-05 5:42 ` [Ocfs2-devel] " Ted Ts'o
2010-08-05 17:42 ` john stultz
2010-08-05 17:42 ` [Ocfs2-devel] " john stultz
2010-08-09 16:06 ` Joel Becker [this message]
2010-08-09 16:06 ` Joel Becker
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=20100809160652.GA4743@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=eric.whitney@hp.com \
--cc=johnstul@us.ibm.com \
--cc=kmannth@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--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.