public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, olof@austin.ibm.com
Subject: Re: [PATCH] .text page fault SMP scalability optimization
Date: Wed, 19 Oct 2005 11:06:32 +0200	[thread overview]
Message-ID: <20051019090632.GC30541@x30.random> (raw)
In-Reply-To: <20051019011420.032ccd6d.akpm@osdl.org>

On Wed, Oct 19, 2005 at 01:14:20AM -0700, Andrew Morton wrote:
> How strange.  Do you mena that all CPUs were entering the pagefault handler
> on behalf of the same pte all the time?  That they're staying in lockstep?

Yes.

> If so, there must be a bunch of page_table_lock contention too?

Not really as much. Note also that with latest mainline the ppc64 kernel
was going well even without this patch, it was some older codebase
falling apart, primarly because it was still doing pte_establish there
see:

	young_entry = pte_mkyoung(entry);
	if (!pte_same(young_entry, entry)) {
		ptep_establish(vma, address, pte, young_entry);
		update_mmu_cache(vma, address, young_entry);
		lazy_mmu_prot_update(young_entry);
	}

So those flush actions were a bottleneck when executed by all cpus at
the same time. But some archs still implement it like with the old
codebase, and the patch is quite an obvious optimization that can
clearly avoid useless tlb flushes (and that fixed the problem completely
with the older codebase still dong ptep_establish even on ppc64).

  reply	other threads:[~2005-10-19  9:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19  7:52 [PATCH] .text page fault SMP scalability optimization Andrea Arcangeli
2005-10-19  8:14 ` Andrew Morton
2005-10-19  9:06   ` Andrea Arcangeli [this message]
2005-10-30  6:17     ` Benjamin Herrenschmidt
2005-10-30 14:44       ` Andrea Arcangeli

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=20051019090632.GC30541@x30.random \
    --to=andrea@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@austin.ibm.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