All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: page fault fastpath: Increasing SMP scalability by introducing pte
Date: Sun, 15 Aug 2004 16:17:11 +0200	[thread overview]
Message-ID: <411F7067.8040305@colorfullife.com> (raw)

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.
>
>  
>
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?

--
    Manfred

             reply	other threads:[~2004-08-15 14:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-15 14:17 Manfred Spraul [this message]
2004-08-15 15:10 ` page fault fastpath: Increasing SMP scalability by introducing pte William Lee Irwin III
2004-08-15 19:36 ` Christoph Lameter
2004-08-15 20:06 ` Christoph Lameter
2004-08-16  5:23   ` Manfred Spraul
  -- strict thread matches above, loose matches on Subject: below --
2004-08-15 13:50 Christoph Lameter

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=411F7067.8040305@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=clameter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.