From: "Joachim Deguara" <joachim.deguara@amd.com>
To: "Nick Piggin" <npiggin@suse.de>
Cc: ricklind@us.ibm.com, "lkml List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation update sched-stat.txt
Date: Fri, 20 Jul 2007 09:56:03 +0200 [thread overview]
Message-ID: <200707200956.03872.joachim.deguara@amd.com> (raw)
In-Reply-To: <20070720072522.GB27772@wotan.suse.de>
On Friday 20 July 2007 09:25:22 Nick Piggin wrote:
> On Wed, Jul 18, 2007 at 11:11:30AM +0200, Joachim Deguara wrote:
> > While learning about schedstats I found that the documentation in the
> > tree is old. I updated it and found some interesting stuff like
> > schedstats version 14 is the same as version and version 13 never saw a
> > kernel release! Also there are 6 fields in the current schedstats that
> > are not used anymore. Nick had made them irrelevant in commit
> > 476d139c218e44e045e4bc6d4cc02b010b343939 but never removed them.
> >
> > Thanks to Rick's perl script who I borrowed some of the updated
> > descriptions from.
>
> Ah, thanks, I actually didn't realise there was such good documentation
> there. Patch looks good.
>
> BTW. I have a simple program to do a basic statistical summary of the
> multiprocessor balancing if you are interested and haven't seen it.
Yes I am interested. Actually I started down this road looking to find out if
task migration could be tracked and I saw that got kicked out from early
versions.
Your script could come in useful to link to in the documentation. Rick has a
great page but hasn't been updated in a little while (though still up-to-date
as version 12==14) and his email bounced (though just a config error).
-Joachim
next prev parent reply other threads:[~2007-07-20 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 9:11 Joachim Deguara
2007-07-20 7:25 ` Nick Piggin
2007-07-20 7:56 ` Joachim Deguara [this message]
2007-07-20 8:12 ` Nick Piggin
2007-07-20 14:49 ` Rick Lindsley
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=200707200956.03872.joachim.deguara@amd.com \
--to=joachim.deguara@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=ricklind@us.ibm.com \
/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®