mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <fletch@aracnet.com>
To: lse-tech@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: 23 second kernel compile (aka which patches help scalibility on NUMA)
Date: Fri, 08 Mar 2002 21:47:04 -0800	[thread overview]
Message-ID: <82825246.1015624024@[10.10.2.3]> (raw)

"time make -j32 bzImage" is now down to 23 seconds.
(16 way NUMA-Q, 700MHz P3's, 4Gb RAM).

Below is a description of which patches helped get there.

	Start (2.4.18)
47s	
	{make NUMA local memory allocation work}
	memalloc-15setup                       (Pat Gaughen)
	memalloc-16discont                     (Pat Gaughen)
	pageallocnull fix + force CONFIG_NUMA  (Martin Bligh)
27s
	{O(1) scheduler}
	sched-O1-2.4.18-pre8-K3.patch          (Ingo Molnar)
25s
	{NUMA scheduler}
	numaK3.patch                           (Mike Kravetz)
24s
	{dcache cacheline bouncing fixes}
	dcache/fast_walkA2-2.4.18.patch        (Hanna Linder)
23s

Appling Ingo's patch alone took time from 47s to 30s.
The benefits after the local mem stuff aren't quite as
stunning, but still good.

Top 10 profile hitters left:

 21439 total                                      0.0228
  9112 default_idle                             175.2308
  3364 _text_lock_swap                           62.2963
   790 lru_cache_add                              8.5870
   750 _text_lock_namei                           0.7184
   587 do_anonymous_page                          1.7681
   572 lru_cache_del                             26.0000
   569 do_generic_file_read                       0.5117
   510 __free_pages_ok                            0.9733
   421 _text_lock_dec_and_lock                   17.5417
   318 _text_lock_read_write                      2.6949

Big locks left:

pagemap_lru_lock
20.2% 57.1%  5.4us(  86us)  111us(  16ms)(14.7%)   1014988 42.9% 57.1%    0%  

pagecache_lock
17.5% 31.3%  7.5us(  99us)   52us(4023us)( 2.4%)    631988 68.7% 31.3%    0% 

others:
dcache_lock (much improved, but still work to be done)
BKL (isn't it always ;-)

Planned work next:

1. Try John Stultz's mcslocks 
	(note high max wait vs low max hold currently)
2. Try rmap + pagemap_lru_breakup from Arjan
3. Try radix tree pagecache.
4. Try grafting NUMA-Q page local alloc onto -aa tree
5. Try SGI NUMA zone ordering stuff.
6. [HARD] Break up ZONE_NORMAL between nodes 
   (all currently on node 0).

Any other suggestions are welcome. I'd also be interested
to know if 23s is fast for make bzImage, or if other big
iron machines can kick this around the room.

Thanks,

Martin.

             reply	other threads:[~2002-03-09  7:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09  5:47 Martin J. Bligh [this message]
2002-03-09 16:43 ` Erik Andersen
2002-03-09 17:53   ` Martin J. Bligh
2002-03-09 18:37     ` Fabio Massimo Di Nitto
2002-03-11 18:23   ` Timothy D. Witham
2002-03-11  2:14 ` Andrea Arcangeli
2002-03-11  2:23   ` Rik van Riel
2002-03-11  4:12     ` Andrea Arcangeli
2002-03-11 10:45 ` Denis Vlasenko
2002-03-09 19:44 Dieter Nützel
2002-03-09 20:19 ` Martin J. Bligh
2002-03-09 21:07   ` Andrea Arcangeli
2002-03-10  9:26   ` Samuel Ortiz
2002-03-10 17:13     ` Martin J. Bligh

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='82825246.1015624024@[10.10.2.3]' \
    --to=fletch@aracnet.com \
    --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

all inboxes | Powered by JetHome®