From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Jeff Epler <jepler@unpythonic.net>
Subject: Re: CONFIG_NO_HZ_FULL restricts cpu usage to the equivalent of one in 4.2
Date: Sat, 18 Jul 2015 15:26:14 +0200 [thread overview]
Message-ID: <20150718132613.GD1747@lerouge> (raw)
In-Reply-To: <20150716003218.GA15221@milliways>
On Thu, Jul 16, 2015 at 01:32:18AM +0100, Ken Moffat wrote:
> On Wed, Jul 15, 2015 at 09:11:46PM +0200, Frederic Weisbecker wrote:
> > 2015-07-15 18:27 GMT+02:00 Ken Moffat <zarniwhoop@ntlworld.com>:
> > >
> > > The config differences follow. Perhaps it is actually one of the
> > > subsequent choices that is the problem. And I guess it could still
> > > be a gcc-5.1 issue.
> > >
> > > --- config-4.2-initial 2015-07-15 16:25:12.548005751 +0100
> > > +++ config-4.2-speed-ok 2015-07-15 17:00:50.919998703 +0100
> > > @@ -104,11 +104,8 @@
> > > CONFIG_TICK_ONESHOT=y
> > > CONFIG_NO_HZ_COMMON=y
> > > # CONFIG_HZ_PERIODIC is not set
> > > -# CONFIG_NO_HZ_IDLE is not set
> > > -CONFIG_NO_HZ_FULL=y
> > > -CONFIG_NO_HZ_FULL_ALL=y
> >
> > You had CONFIG_NO_HZ_FULL_ALL enabled? Because that would indeed
> > produce that effect since it isolates all CPUs but 0 off sched
> > domains.
> >
> > Which means that basically only CPU 0 runs user tasks unless you
> > forces these otherwise.
>
> Thanks. I'll put it down to a bad .config choice, although it was
> fine on early 4.1.
Yeah we decided to include the nohz_full on cpu_isolated_map recently,
except CPU 0.
> While I was starting to bisect, I noticed that
> on the A10 everything was happening on CPU 0 - not sure if that was
> happening on the original box, but for the moment it sounds likely.
>
> ĸen
> --
> This one goes up to eleven!
prev parent reply other threads:[~2015-07-18 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 16:27 CONFIG_NO_HZ_FULL restricts cpu usage to the equivalent of one in 4.2 Ken Moffat
2015-07-15 19:05 ` Andy Lutomirski
2015-07-16 0:34 ` Ken Moffat
2015-07-15 19:11 ` Frederic Weisbecker
2015-07-16 0:32 ` Ken Moffat
2015-07-18 13:26 ` Frederic Weisbecker [this message]
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=20150718132613.GD1747@lerouge \
--to=fweisbec@gmail.com \
--cc=jepler@unpythonic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zarniwhoop@ntlworld.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