From: Frederic Weisbecker <fweisbec@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Jeff Mahoney <jeffm@suse.com>,
Alexander Beregalov <a.beregalov@gmail.com>,
Chris Mason <chris.mason@oracle.com>
Subject: [PATCH 0/7] kill-the-bkl/reiserfs performances updates
Date: Fri, 8 May 2009 20:35:17 +0200 [thread overview]
Message-ID: <1241807725-6263-1-git-send-email-fweisbec@gmail.com> (raw)
Hi Al, everyone,
This patchset is the result of some lock tracing and analysis.
After doing a dbench test on SMP (2 CPUS) with 100 procs during
about 300 secs, I get the following throughput:
With the bkl:
40 MB/s
With the write lock before this patchset:
31 MB/s
With the write lock after this patchset:
36 MB/s
There is still some work to do but it's a good progress.
It seems to depend on the remaining disk space, sometimes I reach
almost the same performances, sometimes it's lower.
For those who want to test it against -rc4, you can pull on the tree
described below, it's a migration of the reiserfs work that was done
in Ingo's tip:core/kill-the-bkl + this patchset.
Thanks,
Frederic.
The following changes since commit e26767ea29f0eb3271e03ba5355c645e2b39939f:
Frederic Weisbecker (1):
kill-the-BKL/reiserfs: release the write lock on flush_commit_list()
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
reiserfs/kill-the-bkl
Frederic Weisbecker (7):
kill-the-BKL/reiserfs: add reiserfs_cond_resched()
kill-the-bkl/reiserfs: conditionaly release the write lock on fs_changed()
kill-the-bkl/reiserfs: lock only once on reiserfs_get_block()
kill-the-bkl/reiserfs: don't hold the write recursively in reiserfs_lookup()
kill-the-bkl/reiserfs: reduce number of contentions in search_by_key()
kill-the-bkl/reiserfs: factorize the locking in reiserfs_write_end()
kill-the-bkl/reiserfs: use mutex_lock in reiserfs_mutex_lock_safe
fs/reiserfs/inode.c | 44 +++++++++++++++++++++++++-----------------
fs/reiserfs/journal.c | 8 ++----
fs/reiserfs/namei.c | 15 ++++++++++---
fs/reiserfs/stree.c | 12 ++++++++++-
include/linux/reiserfs_fs.h | 17 +++++++++++++--
5 files changed, 65 insertions(+), 31 deletions(-)
next reply other threads:[~2009-05-08 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 18:35 Frederic Weisbecker [this message]
2009-05-08 18:35 ` [PATCH 1/7] kill-the-BKL/reiserfs: add reiserfs_cond_resched() Frederic Weisbecker
2009-05-08 18:35 ` [PATCH 2/7] kill-the-bkl/reiserfs: conditionaly release the write lock on fs_changed() Frederic Weisbecker
2009-05-08 18:35 ` [PATCH 3/7] kill-the-bkl/reiserfs: lock only once on reiserfs_get_block() Frederic Weisbecker
2009-05-08 18:35 ` [PATCH 4/7] kill-the-bkl/reiserfs: don't hold the write recursively in reiserfs_lookup() Frederic Weisbecker
2009-05-08 18:35 ` [PATCH 5/7] kill-the-bkl/reiserfs: reduce number of contentions in search_by_key() Frederic Weisbecker
2009-05-08 18:35 ` [PATCH 6/7] kill-the-bkl/reiserfs: factorize the locking in reiserfs_write_end() Frederic Weisbecker
2009-05-08 18:35 ` [PATCH 7/7] kill-the-bkl/reiserfs: use mutex_lock in reiserfs_mutex_lock_safe Frederic Weisbecker
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=1241807725-6263-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=a.beregalov@gmail.com \
--cc=chris.mason@oracle.com \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome