From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, davidm@hpl.hp.com
Subject: Re: 2.6.8.1-mm3
Date: Fri, 20 Aug 2004 15:56:10 -0400 [thread overview]
Message-ID: <200408201556.10806.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20040820115541.3e68c5be.akpm@osdl.org>
On Friday, August 20, 2004 2:55 pm, Andrew Morton wrote:
> > Here's the output part way through a kernbench run:
>
> (This doesn't sound like the sort of workload which people would buy an
> Altix for?)
No, but other people are working on that stuff (e.g. Christoph's page faulting
code). That said, good multiuser performance is important on big boxes too.
> > 27081955 ia64_pal_call_static 141051.8490
> > 3175264 ia64_load_scratch_fpregs 49613.5000
> > 3166434 ia64_save_scratch_fpregs 49475.5312
>
> What do the above three mean?
ia64_pal_call_static is part of the idle path. Puts the CPU into low power
state. The save and restore fp regs I think are due to the fact that integer
multiply uses fp regs, David? They're also preserved across PROM calls, but
we shouldn't be preserving them unless necessary.
> > 1603765 ia64_spinlock_contention 16705.8854
>
> That's 0.04% of total non-idle CPU time. This seems wrong.
The time between resetting the profiling buffer and collecting the profile was
small, and was before kernbench had started 2048 threads, so most of the CPUs
were idle. I can do a longer run now that the profiling stuff seems to work.
Thanks,
Jesse
next prev parent reply other threads:[~2004-08-20 19:57 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 10:19 2.6.8.1-mm3 Andrew Morton
2004-08-20 11:25 ` [PATCH] 2.6.8.1-mm3, fix visws kernel build Andrey Panin
2004-08-20 11:46 ` 2.6.8.1-mm3 Russell King
2004-08-20 11:47 ` [PATCH] 2.6.8.1-mm3, fix qla1280 build on visws Andrey Panin
2004-08-20 15:44 ` 2.6.8.1-mm3 Jesse Barnes
2004-08-20 16:57 ` 2.6.8.1-mm3 Jesse Barnes
2004-08-20 17:08 ` 2.6.8.1-mm3 Jesse Barnes
2004-08-20 18:55 ` 2.6.8.1-mm3 Andrew Morton
2004-08-20 19:56 ` Jesse Barnes [this message]
2004-08-20 20:02 ` 2.6.8.1-mm3 William Lee Irwin III
2004-08-20 23:31 ` 2.6.8.1-mm3 Anton Blanchard
2004-08-21 0:03 ` 2.6.8.1-mm3 William Lee Irwin III
2004-08-21 7:04 ` 2.6.8.1-mm3 Martin J. Bligh
2004-08-21 15:22 ` 2.6.8.1-mm3 William Lee Irwin III
2004-08-21 19:59 ` 2.6.8.1-mm3 Jesse Barnes
2004-08-21 20:24 ` 2.6.8.1-mm3 William Lee Irwin III
2004-08-21 20:35 ` 2.6.8.1-mm3 Jesse Barnes
2004-08-23 9:02 ` 2.6.8.1-mm3 David Mosberger
2004-08-23 16:27 ` 2.6.8.1-mm3 wli
2004-08-23 18:18 ` 2.6.8.1-mm3 Jesse Barnes
2004-08-24 7:24 ` 2.6.8.1-mm3 David Mosberger
2004-08-20 18:04 ` 2.6.8.1-mm3 lockmeter on 512p w/kernbench Jesse Barnes
2004-09-10 16:25 ` Greg Edwards
2004-08-20 18:46 ` 2.6.8.1-mm3 Jesse Barnes
2004-08-21 1:26 ` 2.6.8.1-mm3 Nick Piggin
2004-08-21 20:05 ` 2.6.8.1-mm3 Jesse Barnes
2004-08-22 1:27 ` 2.6.8.1-mm3 Jesse Barnes
2004-08-22 2:11 ` 2.6.8.1-mm3 Nick Piggin
2004-08-22 15:44 ` 2.6.8.1-mm3 Jesse Barnes
2004-08-20 17:38 ` 2.6.8.1-mm3 (build failture w/ CONFIG_NUMA) mita akinobu
2004-08-20 17:55 ` Jesse Barnes
2004-08-20 18:12 ` 2.6.8.1-mm3 (compile stats) John Cherry
2004-08-21 18:54 ` Herbert Poetzl
2004-08-21 17:37 ` 2.6.8.1-mm3 William Lee Irwin III
2004-08-22 13:02 ` 2.6.8.1-mm3 William Lee Irwin III
2004-08-21 18:51 ` 2.6.8.1-mm3 R. J. Wysocki
2004-08-22 4:32 ` 2.6.8.1-mm3 Thomas Davis
2004-08-22 4:48 ` 2.6.8.1-mm3 Andrew Morton
2004-08-22 4:58 ` 2.6.8.1-mm3 Nick Piggin
2004-08-22 6:26 ` 2.6.8.1-mm3 Thomas Davis
2004-08-22 6:51 ` 2.6.8.1-mm3 Pete Zaitcev
2004-08-22 15:11 ` 2.6.8.1-mm3 Bartlomiej Zolnierkiewicz
2004-08-21 14:43 2.6.8.1-mm3 Mikael Pettersson
2004-08-21 16:02 ` 2.6.8.1-mm3 James Bottomley
2004-08-21 17:15 2.6.8.1-mm3 Mikael Pettersson
2004-08-21 18:38 2.6.8.1-mm3 Mikael Pettersson
2004-08-21 19:14 ` 2.6.8.1-mm3 Patrick Mansfield
2004-08-21 19:24 ` 2.6.8.1-mm3 James Bottomley
2004-08-21 21:47 ` 2.6.8.1-mm3 Matthew Wilcox
2004-08-25 3:50 ` 2.6.8.1-mm3 James Bottomley
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=200408201556.10806.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.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®