From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Hanna Linder <hannal@us.ibm.com>,
linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net,
viro@math.psu.edu
Subject: Re: [Lse-tech] lockmeter results comparing 2.4.17, 2.5.3, and 2.5.5
Date: Wed, 27 Feb 2002 12:01:58 -0800 [thread overview]
Message-ID: <86760000.1014840118@flay> (raw)
In-Reply-To: <3C7D374B.4621F9BA@zip.com.au>
In-Reply-To: <10460000.1014833979@w-hlinder.des>, <10460000.1014833979@w-hlinder.des> <67850000.1014834875@flay> <3C7D374B.4621F9BA@zip.com.au>
> inode_lock hold times are a problem for other reasons. Leaving this
> unfixed makes the preepmtible kernel rather pointless.... An ideal
> fix would be to release inodes based on VM pressure against their backing
> page. But I don't think anyone's started looking at inode_lock yet.
>
> The big one is lru_list_lock, of course. I'll be releasing code in
> the next couple of days which should take that off the map. Testing
> would be appreciated.
Seeing as people seem to be interested ... there are some big holders
of BKL around too - do_exit shows up badly (50ms in the data Hanna
posted, and I've seen that a lot before). I've seen sync_old_buffers
hold the BKL for 64ms on an 8way Specweb99 run (22Gb of RAM?)
(though this was on an older 2.4 kernel, and might be fixed by now).
M.
next prev parent reply other threads:[~2002-02-27 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 18:19 lockmeter results comparing 2.4.17, 2.5.3, and 2.5.5 Hanna Linder
2002-02-27 18:34 ` [Lse-tech] " Martin J. Bligh
2002-02-27 19:27 ` Linus Torvalds
2002-02-27 19:45 ` Andrew Morton
2002-02-27 19:57 ` Hanna Linder
2002-02-28 8:31 ` Ravikiran G Thirumalai
2002-02-27 20:01 ` Martin J. Bligh [this message]
2002-02-27 20:15 ` Andrew Morton
2002-02-27 21:31 ` Linus Torvalds
2002-02-27 21:48 ` Alexander Viro
2002-02-27 23:14 ` Hanna Linder
2002-02-27 23:32 ` Hanna Linder
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 21:30 Niels Christiansen
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=86760000.1014840118@flay \
--to=martin.bligh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=hannal@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=viro@math.psu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox