From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Erich Focht <efocht@ess.nec.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: LSE <lse-tech@lists.sourceforge.net>, Ingo Molnar <mingo@elte.hu>,
Michael Hohnbaum <hohnbaum@us.ibm.com>
Subject: Re: [Lse-tech] [PATCH 1/2] node affine NUMA scheduler
Date: Sat, 21 Sep 2002 09:46:05 -0700 [thread overview]
Message-ID: <598631797.1032601564@[10.10.2.3]> (raw)
In-Reply-To: <597807912.1032600740@[10.10.2.3]>
>> Anyway, I'm giving your code a quick spin ... will give you some
>> results later ;-)
>
> Hmmm .... well I ran the One True Benchmark (tm). The patch
> *increased* my kernel compile time from about 20s to about 28s.
> Not sure I like that idea ;-) Anything you'd like tweaked, or
> more info? Both user and system time were up ... I'll grab a
> profile of kernel stuff.
>From the below, I'd suggest you're getting pages off the wrong
nodes: do_anonymous_page is page zeroing, and rmqueue the buddy
allocator. Are you sure the current->node thing is getting set
correctly? I'll try backing out your alloc_pages tweaking, and
see what happens.
An old compile off 2.5.31-mm1 + extras (I don't have 37, but similar)
87elapse133639 total 0.1390
74447 default_idle
6887 do_anonymous_page
4456 page_remove_rmap
4082 handle_mm_fault
3733 .text.lock.namei
2512 page_add_rmap
2187 __generic_copy_from_user
1989 rmqueue
1964 .text.lock.dec_and_lock
1761 vm_enough_memory
1631 file_read_actor
1599 zap_pte_range
1507 __free_pages_ok
1323 find_get_page
1117 do_no_page
1097 get_empty_filp
1023 link_path_walk
2.5.37-mm1
256745 total 0.2584
82934 default_idle
38978 do_anonymous_page
36533 rmqueue
35099 __free_pages_ok
5551 page_remove_rmap
4694 handle_mm_fault
3166 page_add_rmap
2904 do_no_page
2674 .text.lock.namei
2566 __alloc_pages
2526 zap_pte_range
2306 __generic_copy_from_user
2218 file_read_actor
1803 vm_enough_memory
1789 do_wp_page
1557 .text.lock.dec_and_lock
1414 find_get_page
1251 do_softirq
1123 release_pages
1086 link_path_walk
1072 get_empty_filp
1038 schedule
next prev parent reply other threads:[~2002-09-21 16:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 9:59 [PATCH 1/2] node affine NUMA scheduler Erich Focht
2002-09-21 10:02 ` [PATCH 2/2] " Erich Focht
2002-09-21 15:55 ` [Lse-tech] [PATCH 1/2] " Martin J. Bligh
2002-09-21 16:32 ` Martin J. Bligh
2002-09-21 16:46 ` Martin J. Bligh [this message]
2002-09-21 17:11 ` Martin J. Bligh
2002-09-21 17:32 ` Erich Focht
2002-09-21 17:38 ` William Lee Irwin III
2002-09-21 23:18 ` William Lee Irwin III
2002-09-22 8:09 ` William Lee Irwin III
2002-09-22 8:30 ` Erich Focht
2002-09-22 17:11 ` Martin J. Bligh
2002-09-22 19:20 ` Martin J. Bligh
2002-09-22 21:59 ` Erich Focht
2002-09-22 22:36 ` William Lee Irwin III
2002-09-22 22:51 ` Martin J. Bligh
2002-09-23 18:19 ` node affine NUMA scheduler: simple benchmark Erich Focht
2002-09-22 10:35 ` [Lse-tech] [PATCH 1/2] node affine NUMA scheduler Erich Focht
2002-09-22 10:45 ` Erich Focht
2002-09-22 14:57 ` Martin J. Bligh
2002-09-23 18:38 ` Erich Focht
2002-09-23 18:47 ` Martin J. Bligh
2002-09-24 21:04 ` Erich Focht
2002-09-24 21:17 ` Martin J. Bligh
2002-09-22 15:52 ` Martin J. Bligh
2002-09-22 19:24 ` Martin J. Bligh
2002-09-24 23:59 ` Matthew Dobson
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='598631797.1032601564@[10.10.2.3]' \
--to=mbligh@aracnet.com \
--cc=efocht@ess.nec.de \
--cc=hohnbaum@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).