From: Nick Piggin <nickpiggin@yahoo.com.au>
To: markw@osdl.org
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: 2.6.5-mm5
Date: Sun, 18 Apr 2004 19:20:36 +1000 [thread overview]
Message-ID: <40824864.7060106@yahoo.com.au> (raw)
In-Reply-To: <200404162303.i3GN3h231348@mail.osdl.org>
markw@osdl.org wrote:
>
> I do already have CONFIG_IRQBALANCE=y. Is that the interrupt balancing?
> I'll go ahead and get that schedstat data for you.
>
Hi Mark,
Just another question (I think you've already told me once
but I can't remember :P). Do you have HT enabled on your
system? If so, you should have CONFIG_SCHED_SMT=y with -mm
kernels. If not, did you get to the bottom of why oprofile
with linus kernels says the system is P4 / Xeon, while with
mm kernels, it is a P4 / Xeon with 2 hyper-threads?
next prev parent reply other threads:[~2004-04-18 9:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 5:17 2.6.5-mm5 Andrew Morton
2004-04-13 7:38 ` 2.6.5-mm5 Kurt Fitzner
2004-04-13 7:56 ` 2.6.5-mm5 Nick Piggin
2004-04-13 8:07 ` 2.6.5-mm5 devpts filesystem doesn't work Helge Hafting
2004-04-13 8:11 ` Andrew Morton
2004-04-13 8:36 ` Sean Neakums
2004-04-13 8:39 ` Andrew Morton
2004-04-13 9:19 ` Marc-Christian Petersen
2004-04-13 9:26 ` Andrew Morton
2004-04-14 12:38 ` Helge Hafting
2004-04-13 11:36 ` 2.6.5-mm5: no help text for S2IO_NAPI Adrian Bunk
2004-04-13 16:02 ` 2.6.5-mm5 (compile stats) John Cherry
2004-04-15 15:30 ` 2.6.5-mm5 markw
2004-04-15 19:42 ` 2.6.5-mm5 Andrew Morton
2004-04-16 14:51 ` 2.6.5-mm5 markw
2004-04-16 22:59 ` 2.6.5-mm5 Nick Piggin
2004-04-16 23:03 ` 2.6.5-mm5 markw
2004-04-18 9:20 ` Nick Piggin [this message]
2004-04-19 14:53 ` 2.6.5-mm5 markw
2004-04-19 14:51 ` 2.6.5-mm5 markw
2004-04-16 1:57 ` 2.6.5-mm5 Nick Piggin
2004-04-16 10:34 ` 2.6.5-mm5 Ingo Molnar
2004-04-16 14:52 ` 2.6.5-mm5 markw
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=40824864.7060106@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markw@osdl.org \
--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