public inbox for cpufreq@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 100771] When activating ignore_nice_load with governor ondemand performance drops for normal processes.
Date: Thu, 17 Dec 2015 09:09:55 +0000	[thread overview]
Message-ID: <bug-100771-12968-zq3DzuzsVE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-100771-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=100771

--- Comment #7 from Chen Yu <yu.c.chen@intel.com> ---
(In reply to calvaris from comment #6)
> (In reply to Chen Yu from comment #5)
> > Do you mean idle tasks = task_b in above context? Why task_b slows down the
> > normal priority task is because that, the cpufreq decrease due to task_b's
> > high nice value, and task_a is scheduled on the same cpu.
> 
> Yes, I understand that it's what's happenning and I think that is what
> shouldn't happen because, IMHO, it doesn't make sense. I think it should be
> exactly the opposite, as an idle task is scheduled on the same cpu as a
> higher priority one, it should be run at the frequency of the higher one.

Well, currently the cpufreq framework is based on the total load of one CPU,
but not on single task/or a group of tasks. According to your requirement, it
looks like a 'cgroup' cpufreq scheduling. It would be of another new semantic
IMO.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2015-12-17  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-100771-12968@https.bugzilla.kernel.org/>
2015-07-08  5:58 ` [Bug 100771] When activating ignore_nice_load with governor ondemand performance drops for normal processes bugzilla-daemon
2015-12-16 15:11 ` bugzilla-daemon
2015-12-16 16:26 ` bugzilla-daemon
2015-12-17  2:27 ` bugzilla-daemon
2015-12-17  8:33 ` bugzilla-daemon
2015-12-17  9:09 ` bugzilla-daemon [this message]
2015-12-23  6:40 ` bugzilla-daemon

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=bug-100771-12968-zq3DzuzsVE@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@vger.kernel.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