From: Anton Blanchard <anton@samba.org>
To: lse-tech@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: 10.31 second kernel compile
Date: Wed, 13 Mar 2002 19:52:17 +1100 [thread overview]
Message-ID: <20020313085217.GA11658@krispykreme> (raw)
Let the kernel compile benchmarks continue!
hardware: 24 way logical partition, 1.1GHz POWER4, 60G RAM
kernel: 2.5.6 + ppc64 pagetable rework
kernel compiled: 2.4.18 x86 with Martin's config
compiler: gcc 2.95.3 x86 cross compiler
# MAKE="make -j14" /usr/bin/time make -j14 bzImage
...
make[1]: Leaving directory `/home/anton/intel_kernel/linux/arch/i386/boot'
130.63user 71.31system 0:10.31elapsed 1957%CPU (0avgtext+0avgdata 0maxresident)k
Due to the final link and compress stage, there is a fair amount of idle
time at the end of the run. Its going to be hard to push that number
lower by adding cpus.
The profile results below show that kernel time is dominated by the low
level ppc64 pagetable management. We are working to correct this, a lot
of the overhead in __hash_page should be gone soon. The rest of the
profile looks pretty good, do_anonymous_page and lru_cache_add show
up high as they did in Martin's results.
Thanks to Milton Miller who helped with the benchmarking, and the ppc64
team!
Anton
--
anton@samba.org
anton@au.ibm.com
201150 total 0.0668
129051 .idled
43586 .__hash_page ppc64 specific
6714 .local_flush_tlb_range ppc64 specific
2773 .local_flush_tlb_page ppc64 specific
2203 .do_anonymous_page
2059 .lru_cache_add
1379 .__copy_tofrom_user
1220 .hpte_create_valid_pSeriesLP ppc64 LPAR specific
1039 .save_remaining_regs
871 .do_page_fault
575 .plpar_hcall ppc64 LPAR specific
554 .d_lookup
545 .rmqueue
482 .copy_page
475 .__strnlen_user
391 .__free_pages_ok
389 .zap_page_range
366 .atomic_dec_and_lock
296 .__find_get_page
287 .set_page_dirty
278 .page_cache_release
218 .handle_mm_fault
199 .__flush_dcache_icache
175 .schedule
173 .sys_brk
163 .exit_notify
156 .do_no_page
152 .lru_cache_del
147 .__wake_up
146 .copy_page_range
139 .ppc_irq_dispatch_handler
135 .find_vma
131 .__lru_cache_del
128 .fget
126 .link_path_walk
115 .do_generic_file_read
113 .pte_alloc_map
113 .filemap_nopage
109 .clear_user_page
106 .fput
104 .__alloc_pages
101 .nr_free_pages
next reply other threads:[~2002-03-13 10:12 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 8:52 Anton Blanchard [this message]
2002-03-13 14:44 ` 10.31 second kernel compile Martin J. Bligh
2002-03-13 21:44 ` [Lse-tech] " Dave Hansen
2002-03-14 1:07 ` Keith Owens
2002-03-14 11:27 ` Anton Blanchard
2002-03-14 13:16 ` [Lse-tech] " Dipankar Sarma
2002-03-17 13:12 ` some RCU dcache and ratcache results Anton Blanchard
2002-03-14 13:21 ` [Lse-tech] Re: 10.31 second kernel compile Momchil Velikov
2002-03-14 18:33 ` Daniel Phillips
2002-03-15 12:16 ` Chris Wedgwood
2002-03-16 5:12 ` Anton Blanchard
2002-03-15 18:20 ` Linus Torvalds
2002-03-16 11:55 ` Paul Mackerras
2002-03-16 17:25 ` Rik van Riel
2002-03-16 17:57 ` yodaiken
2002-03-16 18:06 ` Linus Torvalds
2002-03-16 18:35 ` yodaiken
2002-03-16 18:45 ` Linus Torvalds
2002-03-16 18:57 ` yodaiken
2002-03-16 19:16 ` Linus Torvalds
2002-03-16 19:43 ` David Mosberger
2002-03-16 19:58 ` Linus Torvalds
2002-03-16 20:08 ` yodaiken
2002-03-16 20:23 ` Linus Torvalds
2002-03-16 20:36 ` David Mosberger
2002-03-16 20:46 ` Linus Torvalds
2002-03-17 1:09 ` Paul Mackerras
2002-03-17 2:08 ` Linus Torvalds
2002-03-16 19:53 ` yodaiken
2002-03-16 20:02 ` Linus Torvalds
2002-03-16 20:25 ` yodaiken
2002-03-27 1:07 ` Richard Henderson
2002-03-16 20:53 ` Alan Cox
2002-03-18 3:07 ` David S. Miller
2002-03-16 15:24 ` Daniel Phillips
2002-03-16 19:01 ` Linus Torvalds
2002-03-16 22:25 ` Daniel Phillips
2002-03-19 16:35 ` Bill Davidsen
2002-03-14 19:05 ` Linus Torvalds
2002-03-19 16:40 ` Bill Davidsen
2002-03-14 18:21 ` Hanna Linder
2002-03-16 5:27 ` Anton Blanchard
2002-03-15 7:12 ` Chris Wedgwood
2002-03-16 6:15 ` 7.52 " Anton Blanchard
2002-03-16 6:42 ` [Lse-tech] " Gerrit Huizenga
2002-03-17 12:34 ` Anton Blanchard
2002-03-17 22:09 ` Theodore Tso
2002-03-18 7:04 ` Jeff Garzik
2002-03-19 18:28 ` Theodore Tso
2002-03-16 8:05 ` Linus Torvalds
2002-03-16 11:04 ` Paul Mackerras
2002-03-16 18:32 ` Linus Torvalds
2002-03-17 2:00 ` Paul Mackerras
2002-03-17 2:40 ` Linus Torvalds
2002-03-17 2:50 ` M. Edward Borasky
2002-03-18 15:08 ` 0.73 " snpe
2002-03-18 19:42 ` 7.52 " Cort Dougan
2002-03-18 20:04 ` Linus Torvalds
2002-03-18 20:23 ` Linus Torvalds
2002-03-18 21:50 ` Rene Herman
2002-03-18 22:36 ` Cort Dougan
2002-03-18 22:47 ` Linus Torvalds
2002-03-18 22:56 ` Cort Dougan
2002-03-18 23:52 ` Paul Mackerras
2002-03-19 0:57 ` Dave Jones
2002-03-19 3:35 ` Jeff Garzik
2002-03-19 0:22 ` David S. Miller
2002-03-19 0:27 ` Cort Dougan
2002-03-19 0:27 ` David S. Miller
2002-03-19 0:36 ` Cort Dougan
2002-03-19 0:38 ` David S. Miller
2002-03-19 1:28 ` Davide Libenzi
2002-03-19 2:42 ` Paul Mackerras
2002-03-27 2:53 ` Richard Henderson
2002-04-02 4:32 ` Linus Torvalds
2002-04-02 10:50 ` Pablo Alcaraz
2002-03-18 21:34 ` Cort Dougan
2002-03-18 22:00 ` Linus Torvalds
2002-03-18 19:37 ` Cort Dougan
2002-03-16 11:54 ` yodaiken
2002-03-16 17:37 ` [Lse-tech] " Martin J. Bligh
2002-03-16 18:57 ` Daniel Egger
2002-03-17 8:18 ` Mike Galbraith
2002-03-17 15:29 ` Martin J. Bligh
2002-03-17 1:45 ` Keith Owens
2002-03-17 13:54 ` David Woodhouse
2002-03-19 16:49 ` Bill Davidsen
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=20020313085217.GA11658@krispykreme \
--to=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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