From: Peter Zijlstra <peterz@infradead.org>
To: Yuyang Du <yuyang.du@intel.com>
Cc: Byungchul Park <byungchul.park@lge.com>,
mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: sync with the cfs_rq when changing sched class
Date: Fri, 14 Aug 2015 10:46:52 +0200 [thread overview]
Message-ID: <20150814084652.GJ16853@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150813232020.GA7780@intel.com>
On Fri, Aug 14, 2015 at 07:20:20AM +0800, Yuyang Du wrote:
> sched: Provide sched class and priority change statistics to task
>
> The sched class and priority changes make substantial impact for
> a task, but we really have not a quantitative understanding of how
> frequent they are, which makes it diffcult to work on many cases
> especially some corner cases. We privide it at task level.
>
> Signed-off-by: Yuyang Du <yuyang.du@intel.com>
Sure we can do that. I would think its fairly rare on regular kernels,
whilst fairly common on -RT kernels where PI is much more active.
next prev parent reply other threads:[~2015-08-14 8:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 5:55 [PATCH] sched: sync with the cfs_rq when changing sched class byungchul.park
2015-08-12 22:41 ` Yuyang Du
2015-08-13 7:19 ` Byungchul Park
2015-08-13 2:30 ` Yuyang Du
2015-08-13 7:46 ` Peter Zijlstra
2015-08-13 8:21 ` Byungchul Park
2015-08-13 2:15 ` Yuyang Du
2015-08-13 10:56 ` Byungchul Park
2015-08-13 15:22 ` Peter Zijlstra
2015-08-13 23:20 ` Yuyang Du
2015-08-14 8:46 ` Peter Zijlstra [this message]
2015-08-15 6:52 ` Byungchul Park
2015-08-15 7:16 ` Byungchul Park
2015-08-13 8:42 ` Byungchul Park
2015-08-14 12:59 ` T. Zhou
2015-08-15 4:24 ` Byungchul Park
2015-08-15 12:34 ` T. Zhou
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=20150814084652.GJ16853@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=byungchul.park@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=yuyang.du@intel.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;
as well as URLs for NNTP newsgroup(s).