From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Rakib Mullick <rakib.mullick@gmail.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: Remove sched_switch completely from runqueue structure.
Date: Wed, 25 Jan 2012 13:33:00 +0100 [thread overview]
Message-ID: <1327494780.2614.60.camel@laptop> (raw)
In-Reply-To: <1327422836.27181.5.camel@localhost.localdomain>
On Tue, 2012-01-24 at 22:33 +0600, Rakib Mullick wrote:
> Currently we don't utilize sched_switch field properly for counting
> context switch numbers. We can remove it.
> But, simply removing sched_switch field from sched_stat output will
> break ABI integrity. So, we make sure
> /proc/sched_stat output remains as it is by hardcoding zero in place
> of sched_switch field's output and remove
> sched_switch from sched_debug output too. And update scheduler-stat
> documentation accordingly.
>
> Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
Thanks
next prev parent reply other threads:[~2012-01-25 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 16:33 [PATCH] sched: Remove sched_switch completely from runqueue structure Rakib Mullick
2012-01-25 12:33 ` Peter Zijlstra [this message]
2012-01-28 12:08 ` [tip:sched/core] sched: Remove sched_switch tip-bot for Rakib Mullick
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=1327494780.2614.60.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rakib.mullick@gmail.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