[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1242266449-21121-1-git-send-email-fweisbec@gmail.com>
Date: Thu, 14 May 2009 04:00:48 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Reiserfs <reiserfs-devel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Jeff Mahoney <jeffm@...e.com>,
Chris Mason <chris.mason@...cle.com>,
Ingo Molnar <mingo@...e.hu>,
Alexander Beregalov <a.beregalov@...il.com>
Subject: [PATCH] kill-the-bkl/reiserfs: update
Hi,
Here is a new patch which increases the performances with
reiserfs using a mutex instead of the bkl.
Now I've compared with dbench on a fresh and empty reiserfs
partition with 64 GB and the results are better with the mutex than with
the bkl.
Also this new patch increases the throughput a bit more.
Dbench on SMP (2 Cpus), Preempt and 100 threads during 400 seconds:
Bkl: 37.6764 MB/sec
Mutex, before this patch: 39.4532 MB/sec
Mutex, after this patch: 40.3758 MB/sec
The following graph shows better the difference:
http://kernel.org/pub/linux/kernel/people/frederic/dbench.pdf
So it looks like on some cases, it is faster (fresh filesystem ?)
and sometimes slower (filesystem already well filled ?).
Of course it is also supposed to be faster on parallel multiple partitions
accesses but I have no benchmark yet to show that.
The following changes since commit 2989c5541d5ab1138e538f8c713f491f7b2416b1:
Frederic Weisbecker (1):
kill-the-bkl/reiserfs: use mutex_lock in reiserfs_mutex_lock_safe
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
kill-the-bkl/reiserfs
Frederic Weisbecker (1):
kill-the-bkl/reiserfs: unlock only when needed in search_by_key
fs/reiserfs/stree.c | 42 ++++++++++++++++++++++++++++++++++--------
1 files changed, 34 insertions(+), 8 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists