From: Lee Revell <rlrevell@joe-job.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Hugh Dickins <hugh@veritas.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16-rc1: 28ms latency when process with lots of swapped memory exits
Date: Tue, 14 Mar 2006 17:38:58 -0500 [thread overview]
Message-ID: <1142375939.24603.33.camel@mindpipe> (raw)
In-Reply-To: <20060314210142.GA23458@elte.hu>
On Tue, 2006-03-14 at 22:01 +0100, Ingo Molnar wrote:
> hm, where does the latency come from? We do have a lockbreaker in
> unmap_vmas():
>
> if (need_resched() ||
> (i_mmap_lock &&
> need_lockbreak(i_mmap_lock))) {
> if (i_mmap_lock) {
> *tlbp = NULL;
> goto out;
> }
> cond_resched();
> }
>
>
> why doesnt this break up the 28ms latency?
>
But the preempt count is >= 2, doesn't that mean some other lock must be
held also, or someone called preempt_disable?
Lee
next prev parent reply other threads:[~2006-03-14 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 16:15 2.6.16-rc1: 28ms latency when process with lots of swapped memory exits Lee Revell
2006-03-14 18:40 ` Hugh Dickins
2006-03-14 19:05 ` Lee Revell
2006-03-14 21:01 ` Ingo Molnar
2006-03-14 22:38 ` Lee Revell [this message]
2006-03-15 7:52 ` Hugh Dickins
2006-03-15 11:19 ` Nick Piggin
2006-03-14 21:22 ` Ingo Molnar
2006-03-14 22:12 ` Lee Revell
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=1142375939.24603.33.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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