From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Erich Focht <efocht@ess.nec.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
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 16:18:10 -0700 [thread overview]
Message-ID: <20020921231810.GA25605@holomorphy.com> (raw)
In-Reply-To: <598631797.1032601564@[10.10.2.3]>
On Sat, Sep 21, 2002 at 09:46:05AM -0700, Martin J. Bligh wrote:
> An old compile off 2.5.31-mm1 + extras (I don't have 37, but similar)
Some 8-quad numbers for 2.5.37 (virgin) follow.
I'll get dcache_rcu and NUMA sched stuff in on the act for round 2.
This is more fs transaction-based (and VM process-spawning overhead)
and not pure I/O throughput so there won't be things like "but
everybody's running at peak I/O bandwidth" obscuring the issues.
real 0m30.854s
c01053ec 16963617 89.009 poll_idle
c0114a48 452526 2.37443 load_balance
c013962c 253666 1.331 get_page_state
c01466de 177354 0.930586 .text.lock.file_table
c0114ec0 150583 0.790117 scheduler_tick
c01547b3 116144 0.609414 .text.lock.namei
c01422ac 94042 0.493444 page_remove_rmap
c0138c24 83293 0.437043 rmqueue
c0141e48 51963 0.272653 page_add_rmap
c012d5ec 37086 0.194592 do_anonymous_page
c01391d0 34454 0.180782 __alloc_pages
c0130e08 32111 0.168488 find_get_page
c0139534 29222 0.153329 nr_free_pages
c012df4c 26734 0.140275 handle_mm_fault
c0146070 25881 0.135799 get_empty_filp
c01a0d2c 25250 0.132488 __generic_copy_from_user
c0111728 22018 0.11553 smp_apic_timer_interrupt
c0112b90 20777 0.109018 pfn_to_nid
c0136238 18410 0.0965983 kmem_cache_free
c0113270 17494 0.091792 do_page_fault
c0138900 17282 0.0906796 __free_pages_ok
c01a0f90 17160 0.0900395 atomic_dec_and_lock
c01a100b 16937 0.0888694 .text.lock.dec_and_lock
next prev parent reply other threads:[~2002-09-21 23:19 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
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 [this message]
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=20020921231810.GA25605@holomorphy.com \
--to=wli@holomorphy.com \
--cc=efocht@ess.nec.de \
--cc=hohnbaum@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
--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