From: Linus Torvalds <torvalds@osdl.org>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: "'Ingo Molnar'" <mingo@elte.hu>,
"'Nick Piggin'" <nickpiggin@yahoo.com.au>,
"'Andrew Morton'" <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: RE: Industry db benchmark result on recent 2.6 kernels
Date: Thu, 31 Mar 2005 12:05:53 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0503311204050.4774@ppc970.osdl.org> (raw)
In-Reply-To: <200503311953.j2VJrog22170@unix-os.sc.intel.com>
On Thu, 31 Mar 2005, Chen, Kenneth W wrote:
>
> No, there are no idle time on the system. If system become I/O bound, we
> would do everything we can to remove that bottleneck, i.e., throw a couple
> hundred GB of memory to the system, or add a couple hundred disk drives,
> etc. Believe it or not, we are currently CPU bound and that's the reason
> why I care about every single cpu cycle being spend in the kernel code.
Can you post oprofile data for a run? Preferably both for the "best case"
2.6.x thing (no point in comparing 2.4.x oprofiles with current) and for
"current kernel", whether that be 2.6.11 or some more recent snapshot?
Linus
next prev parent reply other threads:[~2005-03-31 20:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 19:33 Chen, Kenneth W
2005-03-28 19:50 ` Dave Hansen
2005-03-28 20:01 ` Chen, Kenneth W
2005-03-30 0:00 ` Linus Torvalds
2005-03-30 0:22 ` Chen, Kenneth W
2005-03-30 0:46 ` Chen, Kenneth W
2005-03-30 0:57 ` Linus Torvalds
2005-03-30 1:31 ` Nick Piggin
2005-03-30 1:38 ` Chen, Kenneth W
2005-03-30 1:56 ` Nick Piggin
2005-03-31 14:14 ` Ingo Molnar
2005-03-31 19:53 ` Chen, Kenneth W
2005-03-31 20:05 ` Linus Torvalds [this message]
2005-03-31 20:08 ` Linus Torvalds
2005-03-31 22:14 ` Chen, Kenneth W
2005-03-31 23:35 ` Nick Piggin
2005-04-01 6:05 ` Paul Jackson
2005-04-01 6:34 ` Nick Piggin
2005-04-01 7:19 ` Paul Jackson
2005-04-01 6:46 ` Ingo Molnar
2005-04-01 22:32 ` Chen, Kenneth W
2005-04-01 22:51 ` Linus Torvalds
2005-04-02 2:19 ` Nick Piggin
2005-04-04 1:40 ` Kevin Puetz
2005-04-02 1:44 ` Paul Jackson
2005-04-02 2:05 ` Chen, Kenneth W
2005-04-02 2:38 ` Paul Jackson
2005-04-03 6:36 ` David Lang
2005-04-03 6:53 ` Andreas Dilger
2005-04-03 7:23 ` David Lang
2005-04-03 7:38 ` Nick Piggin
2005-04-01 6:59 ` Ingo Molnar
2005-04-01 9:29 ` Paul Jackson
2005-04-01 10:34 ` Ingo Molnar
2005-04-01 14:39 ` Paul Jackson
2005-04-01 4:52 ` Ingo Molnar
2005-04-01 5:14 ` Chen, Kenneth W
2005-04-01 22:51 ` Chen, Kenneth W
2005-04-01 16:34 Manfred Spraul
2005-04-02 1:00 Chen, Kenneth W
2005-04-02 2:12 ` Nick Piggin
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=Pine.LNX.4.58.0503311204050.4774@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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®