From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] lockmeter results comparing 2.4.17, 2.5.3, and 2.5.5
Date: Wed, 27 Feb 2002 21:31:17 +0000 (UTC) [thread overview]
Message-ID: <a5jj75$cuk$1@penguin.transmeta.com> (raw)
In-Reply-To: <3C7D374B.4621F9BA@zip.com.au> <3C7D374B.4621F9BA@zip.com.au> <86760000.1014840118@flay> <3C7D3E5A.490D939D@zip.com.au>
In article <3C7D3E5A.490D939D@zip.com.au>,
Andrew Morton <akpm@zip.com.au> wrote:
>"Martin J. Bligh" wrote:
>>
>> 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).
>
>That'll be where exit() takes down the tasks's address spaces.
>zap_page_range(). That's a nasty one.
No, lock_kernel happens after exit_mm, and in fact I suspect it's not
really needed at all any more except for the current "sem_exit()". I
think most everything else is threaded already.
(Hmm.. Maybe disassociate_ctty() too).
So minimizing the BLK footprint in do_exit() should be pretty much
trivial: all the really interesting stuff should be ok already.
Linus
next prev parent reply other threads:[~2002-02-27 21:33 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
2002-02-27 20:15 ` Andrew Morton
2002-02-27 21:31 ` Linus Torvalds [this message]
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='a5jj75$cuk$1@penguin.transmeta.com' \
--to=torvalds@transmeta.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