mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: Luis Henriques <henrix@sapo.pt>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 -tip] sched: Clean unused fields from struct rq
Date: Tue, 17 Mar 2009 21:33:19 -0400	[thread overview]
Message-ID: <49C04F5F.1020700@novell.com> (raw)
In-Reply-To: <20090318002327.GA2382@hades.domain.com>

[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]

Luis Henriques wrote:
> On Wed, Mar 18, 2009 at 01:09:29AM +0100, Peter Zijlstra wrote:
>   
>> On Wed, 2009-03-18 at 00:03 +0000, Luis Henriques wrote:
>>     
>>> Since they are used on in statistics and are always set to zero, the following
>>> frields from struct rq have been removed: yld_exp_empty, yld_act_empty and
>>> yld_both_empty.
>>>
>>> Signed-off-by: Luis Henriques <henrix@sapo.pt>
>>> ---
>>>       
>>> +++ b/kernel/sched_stats.h
>>> @@ -26,9 +26,8 @@ static int show_schedstat(struct seq_file *seq, void *v)
>>>  
>>>  		/* runqueue-specific stats */
>>>  		seq_printf(seq,
>>> -		    "cpu%d %u %u %u %u %u %u %u %u %u %llu %llu %lu",
>>> -		    cpu, rq->yld_both_empty,
>>> -		    rq->yld_act_empty, rq->yld_exp_empty, rq->yld_count,
>>> +		    "cpu%d %u %u %u %u %u %u %llu %llu %lu",
>>> +		    cpu, rq->yld_count,
>>>  		    rq->sched_switch, rq->sched_count, rq->sched_goidle,
>>>  		    rq->ttwu_count, rq->ttwu_local,
>>>  		    rq->rq_cpu_time,
>>>       
>> I think this bit is ABI, so you either have to bump the version number
>> or emit 0s, iirc gregory touched some of that last -- or at least wrote
>> userspace for it..
>>     
>
> Hmm... you're right.  I should have though about that.  Anyway, what is the
> the best approach here?
>
> I know that changes in ABI shall not break anything, but just increasing the
> version number will really solve the issue?  Will userspace care for this?
> On the other hand, just writting 0s does not sound interesting either...
>
>   
Hi Luis,
  My app does check the version number, so bumping it is probably the
best solution.   Be sure to keep me in the loop about whether this patch
gets merged and I will be sure to update it to handle the new version.

Regards,
-Greg






[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-03-18  1:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18  0:03 Luis Henriques
2009-03-18  0:09 ` Peter Zijlstra
2009-03-18  0:23   ` Luis Henriques
2009-03-18  1:33     ` Gregory Haskins [this message]
2009-03-18  8:51       ` Peter Zijlstra
2009-03-18 20:08       ` Luis Henriques
2009-03-18  8:50     ` Peter Zijlstra

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=49C04F5F.1020700@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

Powered by JetHome