public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Ian Stirling <ian.stirling@mauve.plus.com>,
	Diego Calleja <diegocg@gmail.com>,
	linux-kernel@vger.kernel.org, hugh@veritas.com, akpm@osdl.org,
	">" <dmccr@us.ibm.com>
Subject: Re: Shared page tables patch... some results
Date: Thu, 14 Sep 2006 10:45:37 -0700	[thread overview]
Message-ID: <1158255937.18314.29.camel@localhost.localdomain> (raw)
In-Reply-To: <3282373b0609141116n1bce85b3u38924491146a89f2@mail.gmail.com>

On Aug 15, 2006 3:34 AM, Arjan van de Ven wrote:

> 
> Hi,
> 
> until OLS of this year, most people thought that Dave's shared page
> table patch was effectively a database-only hack, and thus not all that
> interesting...
> 
> however it's also possible to use shared page tables for shared
> libraries, and thus the gain is MUCH wider in scope. Dave has been so
> kind as to send me his latest patch, and I've done some measurements on
> my new x86-64 test machine (which runs FC6-test2)...
> 
> and the result is interesting:
> Just booting into runlevel 5 and logging into gnome (without starting
> any apps) gets a sharing of 1284 pte pages! This means that five
> megabytes (!!) of memory is saved, and countless pagefaults are avoided.
> 

The shared page table patch also gives a nice boost to the fork speed as
tested on a woodcrest machine using lmbench-3.0-a7.

2.6.18-rc4 with shared page table enabled (usec):
fork 136
exec 303
sh   828

2.6.18-rc4 without shared page table (usec):
fork 179
exec 364
sh   949

The test was done with the lmbench option to pin both parent and child
onto the same cpu core, and lmbench includes the overhead of calling
sched_setaffinity.

Tim Chen

      parent reply	other threads:[~2006-09-14 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 10:34 Shared page tables patch... some results Arjan van de Ven
2006-08-15 14:41 ` Andi Kleen
2006-08-15 14:45   ` Arjan van de Ven
2006-08-15 15:59 ` Diego Calleja
2006-08-15 19:29   ` Ian Stirling
     [not found] ` <3282373b0609141116n1bce85b3u38924491146a89f2@mail.gmail.com>
2006-09-14 17:45   ` Tim Chen [this message]

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=1158255937.18314.29.camel@localhost.localdomain \
    --to=tim.c.chen@linux.intel.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=diegocg@gmail.com \
    --cc=dmccr@us.ibm.com \
    --cc=hugh@veritas.com \
    --cc=ian.stirling@mauve.plus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox