From: Gregory Haskins <ghaskins@novell.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Luis Henriques <henrix@sapo.pt>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 -tip] sched: Clean unused fields from struct rq
Date: Tue, 24 Mar 2009 11:59:34 -0400 [thread overview]
Message-ID: <49C90366.2000905@novell.com> (raw)
In-Reply-To: <20090324154130.GC31143@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 2310 bytes --]
Ingo Molnar wrote:
> * Gregory Haskins <ghaskins@novell.com> wrote:
>
>
>> Ingo Molnar wrote:
>>
>>> * Luis Henriques <henrix@sapo.pt> wrote:
>>>
>>>
>>>
>>>> On Wed, Mar 18, 2009 at 10:51:37PM +0000, Luis Henriques wrote:
>>>>
>>>>
>>>>> Since they are used on in statistics and are always set to zero, the following
>>>>> fields from struct rq have been removed: yld_exp_empty, yld_act_empty and
>>>>> yld_both_empty.
>>>>>
>>>>> Both Sched Debug and SCHEDSTAT_VERSION versions has also been incremented since
>>>>> ABIs have been changed.
>>>>>
>>>>>
>>>>>
>>>> Hi Ingo,
>>>>
>>>> Sorry to bother you but I can not find this patch in -tip. Just
>>>> would like to confirm with you that it was NACK'ed or you just
>>>> forgot to merge it to the tree.
>>>>
>>>>
>>> Was held up by the schedstat tool discussions. Please resend the
>>> patch with a link to the updated tool in the commit log perhaps (if
>>> such a link exists), and with Gregory's ack in place.
>>>
>>> Thanks,
>>>
>>> Ingo
>>>
>>>
>> Hi Ingo,
>> I was waiting to merge the tool patch until I was sure this would be
>> your blessed v15 of the ABI. If you are comfy with the kernel patch but
>> want the tool updated before the kernel, I can do that, no problem. The
>> only thing that I ask is that if for some reason this kernel patch
>> doesn't make it in, please require any future patches that change this
>> ABI to be versioned > 15 ;)
>>
>
> How about moving schedstat to Documentation/sched/schedstat.c or so?
> It's small and trivial enough, and that way changes would go hand in
> hand with the app.
>
Oh, I misunderstood. The tool patch I was referencing is for my
schedtop tool that is in a separate tree and written in C++. In
retrospect, you probably don't care about the relative state of my tool
coincident with the kernel side change, then. I agree that this other
schedstat tool should probably be in-tree and patched at the same time
as Luis' kernel patch.
FWIW: I have no problem with schedtop.cc going into the kernel as well
if that is what you would like, but I figured I would be burned at the
stake for suggestion such heresy as C++ in the tree ;)
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-03-24 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 22:51 [PATCH v3 -tip] sched: Clean unused fields from struct rq Luis Henriques
2009-03-18 22:54 ` Luis Henriques
2009-03-19 7:49 ` Ingo Molnar
2009-03-19 11:56 ` Gregory Haskins
2009-03-19 18:23 ` Luis Henriques
2009-03-19 18:51 ` Gregory Haskins
2009-03-19 18:43 ` Gregory Haskins
2009-03-23 17:52 ` Luis Henriques
2009-03-24 14:04 ` Ingo Molnar
2009-03-24 15:22 ` Gregory Haskins
2009-03-24 15:41 ` Ingo Molnar
2009-03-24 15:59 ` Gregory Haskins [this message]
2009-03-24 18:22 ` Luis Henriques
2009-03-24 21:04 ` Ingo Molnar
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=49C90366.2000905@novell.com \
--to=ghaskins@novell.com \
--cc=henrix@sapo.pt \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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