From: Anton Blanchard <anton@samba.org>
To: Momchil Velikov <velco@fadata.bg>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Scalable page cache - take two
Date: Mon, 24 Dec 2001 11:52:58 +1100 [thread overview]
Message-ID: <20011224005258.GB15536@krispykreme> (raw)
In-Reply-To: <87bsgp7fcq.fsf@fadata.bg>
In-Reply-To: <87bsgp7fcq.fsf@fadata.bg>
Hi,
> This is the second mutation of the scalable page cache patch. It:
I ran the dbench test over it just to annoy Andrew:
http://samba.org/~anton/linux/pagecache_locking/2/
This is the still 12 way ppc64, the results are similar to the last
test. It confirms that the current pagecache locking is a bottleneck
for larger SMP machines.
We quickly hit the following spinlocks with the pagecache lock out of
the way:
ext2_get_block: BKL
refile_buffer: lru_list_lock
remove_from_queues: lru_list_lock
try_to_free_buffers: lru_list_lock
d_lookup: dcache_lock
ext2_discard_prealloc: BKL
Is someone working on removing the BKL from ext2 in 2.5?
Anton
next prev parent reply other threads:[~2001-12-24 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-23 22:15 [PATCH] Scalable page cache - take two Momchil Velikov
2001-12-24 0:28 ` William Lee Irwin III
2001-12-24 0:52 ` Anton Blanchard [this message]
2001-12-27 6:15 ` Daniel Phillips
2001-12-24 17:08 ` Heinz Diehl
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=20011224005258.GB15536@krispykreme \
--to=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=velco@fadata.bg \
/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