From: Arjan van de Ven <arjan@linux.intel.com>
To: Jes Sorensen <jes@sgi.com>
Cc: ak@suse.de, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch 1/3] prefetch the mmap_sem in the fault path
Date: Thu, 23 Feb 2006 13:39:16 +0100 [thread overview]
Message-ID: <1140698357.4672.46.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <yq0zmkigsxf.fsf@jaguar.mkp.net>
On Thu, 2006-02-23 at 07:29 -0500, Jes Sorensen wrote:
> >>>>> "Arjan" == Arjan van de Ven <arjan@intel.linux.com> writes:
>
> Arjan> In a micro-benchmark that stresses the pagefault path, the
> Arjan> down_read_trylock on the mmap_sem showed up quite high on the
> Arjan> profile. Turns out this lock is bouncing between cpus quite a
> Arjan> bit and thus is cache-cold a lot. This patch prefetches the
> Arjan> lock (for write) as early as possible (and before some other
> Arjan> somewhat expensive operations). With this patch, the
> Arjan> down_read_trylock basically fell out of the top of profile.
>
> Out of curiousity, how big was the box used for testing? It might be
> worth investigating if anything can be done to reduce the number of
> times that lock is taken in the first place.
>
> After all, what's a pain on a 4-way tends to be an utter nightmare on
> a 16-way ;(
most of it was done on a 2 way, but some tests were done on a 4-way.
next prev parent reply other threads:[~2006-02-23 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1140686152.2972.25.camel@laptopd505.fenrus.org>
2006-02-23 9:30 ` Arjan van de Ven
2006-02-23 9:39 ` Andi Kleen
2006-02-23 9:47 ` Arjan van de Ven
2006-02-23 10:14 ` Andi Kleen
2006-02-23 12:29 ` Jes Sorensen
2006-02-23 12:39 ` Arjan van de Ven [this message]
2006-02-23 4:15 ` Ray Bryant
2006-03-01 0:51 Valerie Henson
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=1140698357.4672.46.camel@laptopd505.fenrus.org \
--to=arjan@linux.intel.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jes@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
all inboxes | Powered by JetHome®