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: Mon, 16 Aug 2004 07:23:48 +0200	[thread overview]
Message-ID: <412044E4.4030409@colorfullife.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408151304190.2470@schroedinger.engr.sgi.com>

Christoph Lameter wrote:

>On Sun, 15 Aug 2004, Manfred Spraul wrote:
>
>  
>
>>Very odd. Why do you see a problem with the page_table_lock but no
>>problem from the mmap semaphore?
>>    
>>
>
>Because there is a only a down_read() call for the mmap semaphore before
>invoking handle_mm_fault. This is a rw semaphore which means that multiple
>processors/processes may be entering handle_mm_fault with a read lock on
>the mmap semaphore.
>  
>
As far as I can see the actual hold times on the page_table_lock are not 
that long and down_read() causes a cache line transfer, too.
But you have answered my question in your first mail: There are 2-5 
spin_lock calls per page fault but only one down_read call.

--
    Manfred

  reply	other threads:[~2004-08-16  5:20 UTC|newest]

Thread overview: 6+ 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
2004-08-15 19:36 ` Christoph Lameter
2004-08-15 20:06 ` Christoph Lameter
2004-08-16  5:23   ` Manfred Spraul [this message]
  -- 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=412044E4.4030409@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.