linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: p4admin@sepura.com
Cc: Christoph@sepura.com, Lameter@sepura.com, christoph@lameter.com,
	linux-mm@kvack.org
Subject: Perforce change 315120
Date: Thu, 10 Nov 2011 18:21:49 +0000	[thread overview]
Message-ID: <E1ROZG1-00063C-Px@serv30.sepura.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 2779 bytes --]

Change 315120 by devtools@devtools_gitimport on 2011/11/10 18:21:26

	commit a600388d28419305aad3c4c0af52c223cf6fa0af
	Author: Zachary Amsden <zach@vmware.com>
	Date:   Sat Sep 3 15:55:04 2005 -0700
	
	    [PATCH] x86: ptep_clear optimization
	
	    Add a new accessor for PTEs, which passes the full hint from the mmu_gather
	    struct; this allows architectures with hardware pagetables to optimize away
	    atomic PTE operations when destroying an address space.  Removing the
	    locked operation should allow better pipelining of memory access in this
	    loop.  I measured an average savings of 30-35 cycles per zap_pte_range on
	    the first 500 destructions on Pentium-M, but I believe the optimization
	    would win more on older processors which still assert the bus lock on xchg
	    for an exclusive cacheline.
	
	    Update: I made some new measurements, and this saves exactly 26 cycles over
	    ptep_get_and_clear on Pentium M.  On P4, with a PAE kernel, this saves 180
	    cycles per ptep_get_and_clear, for a whopping 92160 cycles savings for a
	    full address space destruction.
	
	    pte_clear_full is not yet used, but is provided for future optimizations
	    (in particular, when running inside of a hypervisor that queues page table
	    updates, the full hint allows us to avoid queueing unnecessary page table
	    update for an address space in the process of being destroyed.
	
	    This is not a huge win, but it does help a bit, and sets the stage for
	    further hypervisor optimization of the mm layer on all architectures.
	
	    Signed-off-by: Zachary Amsden <zach@vmware.com>
	    Cc: Christoph Lameter <christoph@lameter.com>
	    Cc: <linux-mm@kvack.org>
	    Signed-off-by: Andrew Morton <akpm@osdl.org>
	    Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Affected files ...

... //sw/components_third_party/linux/git/master/.versions.submit#1698 edit
... //sw/components_third_party/linux/git/master/component/include/asm-generic/pgtable.h#4 edit
... //sw/components_third_party/linux/git/master/component/include/asm-i386/pgtable.h#7 edit
... //sw/components_third_party/linux/git/master/component/mm/memory.c#13 edit

  http://serv30:8666/315120?ac=10


The information in this email is confidential. It is intended
solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any
disclosure, copying, or distribution is prohibited and may be
unlawful. If you have received this email in error please delete
it immediately and contact commercial@sepura.com.

Sepura plc. Registered Office: Radio House, St Andrew’s Road, Cambridge, CB4 1GR, England. Registered in England and Wales. Registration Number 4353801
 

[-- Attachment #2: Type: text/html, Size: 3760 bytes --]

                 reply	other threads:[~2011-11-10 18:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E1ROZG1-00063C-Px@serv30.sepura.co.uk \
    --to=p4admin@sepura.com \
    --cc=Christoph@sepura.com \
    --cc=Lameter@sepura.com \
    --cc=christoph@lameter.com \
    --cc=devtools@sepura.com \
    --cc=linux-mm@kvack.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