mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>,
	clameter@engr.sgi.com, apw@shadowen.org, akpm@osdl.org,
	heiko.carstens@de.ibm.com, bob.picco@hp.com,
	"kamezawa.hiroyu@jp.fujitsu.com" <kamezawa.hiroyu@jp.fujitsu.com>
Subject: [PATCH][2.6.20-rc1-mm1] sparsemem vmem_map optimzed pfn_valid() [0/2]
Date: Sat, 16 Dec 2006 17:31:36 +0900	[thread overview]
Message-ID: <20061216173136.fbc91fa6.kamezawa.hiroyu@jp.fujitsu.com> (raw)

This patch implements pfn_valid() micro optimization.

This uses ia64_pfn_valid() idea to check mem_map is valid or not instead of
sparsemem's logic.

By this, we'll not access mem_section[] in usual ops.

I attaches my easy test result with *micro* benchmark on SMP system.
I'm glad if you give me an advice about testing.

-Kame
==
AIM Independent Resource Benchmark - Suite IX "1.1"

test on 
CPU: Itanium2(madison) 1.3GHz x2, SMP
Memory: memory 8G
2.6.20-rc1-m1 / 
  extreme means  SPARSEMEM_VMEMMAP=n
  vmem_map means SPARSEMEM_VMEMMAP=y + optimze pfn_valid patch.
==
                extreme	    vmem_map
creat-clo       136322      136989  File Creations and Closes per second
page_test       1042187     1076976 System Allocations & Pages per second
brk_test        2678559     2727286 System Memory Allocations per second
signal_test     309525      321052  Signal Traps per second
exec_test       803         801     Program Loads per second
fork_test       9354        9679    Task Creations per second
disk_rr         103766      103970  Random Disk Reads (K) per second
disk_rw         82978       80244   Random Disk Writes (K) per second
disk_rd         802548      872983  Sequential Disk Reads (K) per second
disk_wrt        130342      131408  Sequential Disk Writes (K) per second
disk_cp         107498      107823  Disk Copies (K) per second
sync_disk_rw    800         752     Sync Random Disk Writes (K) per second
sync_disk_wrt   81          78      Sync Sequential Disk Writes (K) per second
sync_disk_cp    84          78      Sync Disk Copies (K) per second
disk_src        44417       44379   Directory Searches per second
mem_rtns_1      3239352     3222140 Dynamic Memory Operations per second
mem_rtns_2      1157321     1155260 Block Memory Operations per second
misc_rtns_1     10799       10993   Auxiliary Loops per second
dir_rtns_1      1276159     1373725 Directory Operations per second
shell_rtns_1    175         176     Shell Scripts per second
shell_rtns_2    174         175     Shell Scripts per second
shell_rtns_3    175         175     Shell Scripts per second
shared_memory   646725      628769  Shared Memory Operations per second
tcp_test        93258       94928   TCP/IP Messages per second
udp_test        177984      177276  UDP/IP DataGrams per second
fifo_test       362774      385434  FIFO Messages per second
stream_pipe     320825      325931  Stream Pipe Messages per second
dgram_pipe      300789      303339  DataGram Pipe Messages per second
pipe_cpy        410539      449521  Pipe Messages per second


             reply	other threads:[~2006-12-16  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16  8:31 KAMEZAWA Hiroyuki [this message]
2006-12-16  8:34 ` [PATCH][2.6.20-rc1-mm1] sparsemem vmem_map optimzed pfn_valid() [1/2] generic arch KAMEZAWA Hiroyuki
2006-12-16  8:35 ` [PATCH][2.6.20-rc1-mm1] sparsemem vmem_map optimzed pfn_valid() [2/2] for ia64 KAMEZAWA Hiroyuki
2006-12-16 18:38 ` [PATCH][2.6.20-rc1-mm1] sparsemem vmem_map optimzed pfn_valid() [0/2] Christoph Lameter
2006-12-17  1:02   ` KAMEZAWA Hiroyuki
2006-12-20 20:06 ` Bob Picco
2006-12-21  0:37   ` KAMEZAWA Hiroyuki

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=20061216173136.fbc91fa6.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=bob.picco@hp.com \
    --cc=clameter@engr.sgi.com \
    --cc=heiko.carstens@de.ibm.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

all inboxes | Powered by JetHome®