From: William Lee Irwin III <wli@holomorphy.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Christoph Lameter <clameter@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: page fault fastpath: Increasing SMP scalability by introducing pte
Date: Sun, 15 Aug 2004 08:10:24 -0700 [thread overview]
Message-ID: <20040815151024.GI11200@holomorphy.com> (raw)
In-Reply-To: <411F7067.8040305@colorfullife.com>
Christoph wrote:
>> Well this is more an idea than a real patch yet. The page_table_lock
>> becomes a bottleneck if more than 4 CPUs are rapidly allocating and using
>> memory. "pft" is a program that measures the performance of page faults on
>> SMP system. It allocates memory simultaneously in multiple threads thereby
>> causing lots of page faults for anonymous pages.
On Sun, Aug 15, 2004 at 04:17:11PM +0200, Manfred Spraul wrote:
> Very odd. Why do you see a problem with the page_table_lock but no
> problem from the mmap semaphore?
> The page fault codepath acquires both.
> How often is the page table lock acquired per page fault? Just once or
> multiple spin_lock calls per page fault? Is the problem contention or
> cache line trashing?
> Do you have profile/lockmeter output? Is the down_read() in
> do_page_fault() a hot spot, too?
->mmap_sem would likely be useful to address as well. A different
structure for vma trees, more amenable to finegrained locking or
lockfree algorithms, would likely be useful there.
-- wli
next prev parent reply other threads:[~2004-08-15 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 14:17 page fault fastpath: Increasing SMP scalability by introducing pte Manfred Spraul
2004-08-15 15:10 ` William Lee Irwin III [this message]
2004-08-15 19:36 ` Christoph Lameter
2004-08-15 20:06 ` Christoph Lameter
2004-08-16 5:23 ` Manfred Spraul
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=20040815151024.GI11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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