From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, Rick Lindsley <ricklind@us.ibm.com>
Subject: Re: [PATCH] schedstats additions
Date: Sat, 04 Sep 2004 19:04:27 +1000 [thread overview]
Message-ID: <4139851B.8070100@yahoo.com.au> (raw)
In-Reply-To: <200409041026.51519.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> Dnia Saturday 04 of September 2004 07:07, Nick Piggin napisał:
>
>>Hi,
>>I have a patch here to provide more useful statistics for me. Basically
>>it moves a lot more of the balancing information into the domains instead
>>of the runqueue, where it is nearly useless on multi-domain setups (eg.
>>SMT+SMP, SMP+NUMA).
>
>
> Which kernel version it is against?
>
-mm3 ... oh yeah that has nicksched in it, sorry that would put a spanner
in the works.
I'll redo it to suit 2.6 if Rick acks it - the main info he needs is still
valid, that is the output format.
Thanks
Nick
next prev parent reply other threads:[~2004-09-04 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 5:07 [PATCH] schedstats additions Nick Piggin
2004-09-04 8:26 ` Rafael J. Wysocki
2004-09-04 9:04 ` Nick Piggin [this message]
2004-09-08 8:09 ` Rick Lindsley
2004-09-08 22:56 ` 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=4139851B.8070100@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ricklind@us.ibm.com \
--cc=rjw@sisk.pl \
/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