From: Peter Zijlstra <peterz@infradead.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Kevin Hilman <khilman@linaro.org>, Ingo Molnar <mingo@redhat.com>,
Tejun Heo <tj@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Linaro Networking <linaro-networking@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [LNG] Re: [Query] Ticks happen in pair for NO_HZ_FULL cores ?
Date: Tue, 7 Jan 2014 09:47:34 +0100 [thread overview]
Message-ID: <20140107084734.GP30183@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKohpo=bzfnb6aBDRX6AfjVoRquTaboO5wmiHfjb=bD0bAgBcA@mail.gmail.com>
On Mon, Dec 23, 2013 at 01:48:02PM +0530, Viresh Kumar wrote:
> *But wouldn't it make sense if we can tell scheduler that don't queue
> these works on a CPU that is running in NO_HZ_FULL mode?*
No,.. that's the wrong way around.
> Also any suggestions on how to get rid of __prandom_timer events on
> such CPUs?
That looks to be a normal unpinned timer, it should migrate to a 'busy'
cpu once the one its running on it going idle.
ISTR people trying to make that active and also migrating on nohz full
or somesuch, just like the workqueues. Forgot what happened with that;
if it got dropped it should probably be ressurected.
next prev parent reply other threads:[~2014-01-07 8:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKohponch=o3nBKTmakA87OiN=HbgnEwJUL23mGkjQiNoJWjWw@mail.gmail.com>
2013-12-11 13:22 ` [Query] Ticks happen in pair for NO_HZ_FULL cores ? Frederic Weisbecker
2013-12-11 21:14 ` Tejun Heo
2013-12-13 0:32 ` Kevin Hilman
2013-12-17 10:35 ` Viresh Kumar
2013-12-17 16:35 ` Kevin Hilman
2013-12-17 16:57 ` Frederic Weisbecker
2013-12-18 4:38 ` Viresh Kumar
2013-12-18 13:51 ` Kevin Hilman
2013-12-18 14:33 ` [LNG] " Viresh Kumar
2013-12-23 8:18 ` Viresh Kumar
2014-01-07 7:49 ` Viresh Kumar
2014-01-07 8:47 ` Peter Zijlstra [this message]
2014-01-07 8:55 ` Viresh Kumar
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=20140107084734.GP30183@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fweisbec@gmail.com \
--cc=khilman@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linaro-networking@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tj@kernel.org \
--cc=viresh.kumar@linaro.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