From: "John Hawkes" <hawkes@sgi.com>
To: "Linux-Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5: push BKL out of llseek
Date: Fri, 1 Feb 2002 11:29:11 -0800 [thread overview]
Message-ID: <01ec01c1ab56$ba7d5e40$6401a8c0@attbi.com> (raw)
From: "Dave Jones" <davej@suse.de>
> did you benchmark with anything other than dbench ?
I've done substantial AIM7 benchmarking on a 28p ia64 NUMA system, and
llseek's BKL usage is a significant contributor to poor scaling. For
500 AIM7 "tasks" and ext2 filesystems, waiting on the BKL consumes about
half of the available CPU cycles, and sys_lseek()'s usage is the most
significant cycle waster, followed by ext2_get_block() and
ext2_write_inode(). Anton's llseek patch from last November does make
a measurable improvement in AIM7 throughput.
--
John Hawkes
hawkes@sgi.com
next reply other threads:[~2002-02-01 19:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 19:29 John Hawkes [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-31 15:39 [PATCH] 2.5: push BKL out of llseek Martin Wirth
2002-01-31 21:06 ` Nigel Gamble
2002-01-30 21:14 Martin Wirth
2002-01-30 0:00 Robert Love
2002-01-30 0:09 ` Linus Torvalds
2002-01-30 0:41 ` Robert Love
2002-01-30 0:52 ` Linus Torvalds
2002-01-30 2:24 ` Robert Love
2002-01-30 1:26 ` Andrew Morton
2002-01-30 2:16 ` Linus Torvalds
2002-01-30 2:20 ` Robert Love
2002-01-30 2:20 ` Andrew Morton
2002-01-30 2:21 ` Dave Jones
2002-01-30 2:37 ` Robert Love
2002-01-30 2:50 ` Nigel Gamble
2002-01-30 3:19 ` Andrew Morton
2002-01-30 9:34 ` Nigel Gamble
2002-01-30 10:36 ` Russell King
2002-01-30 4:54 ` Alexander Viro
2002-01-30 8:00 ` Trond Myklebust
2002-01-30 13:39 ` Robert Love
2002-01-30 4:50 ` Anton Blanchard
2002-01-30 5:03 ` Robert Love
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='01ec01c1ab56$ba7d5e40$6401a8c0@attbi.com' \
--to=hawkes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/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