linux-kernel - Re: Very high CPU load when idle with 3.0-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1306791219.23844.12.camel@twins>
Date:	Mon, 30 May 2011 23:33:39 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	paulmck@...ux.vnet.ibm.com
Cc:	Damien Wyart <damien.wyart@...e.fr>, Ingo Molnar <mingo@...e.hu>,
	Mike Galbraith <efault@....de>, linux-kernel@...r.kernel.org
Subject: Re: Very high CPU load when idle with 3.0-rc1

On Mon, 2011-05-30 at 14:28 -0700, Paul E. McKenney wrote:
> On Mon, May 30, 2011 at 07:19:49PM +0200, Peter Zijlstra wrote:
> > On Mon, 2011-05-30 at 09:23 -0700, Paul E. McKenney wrote:
> > >         sp.sched_priority = RCU_KTHREAD_PRIO;
> > >         sched_setscheduler_nocheck(t, SCHED_FIFO, &sp); 
> > 
> > Why are those things RT tasks anyway? The old ksoftirq runs as a regular
> > task. And once you start boosting things you can boost this into FIFO as
> > well...
> > 
> > just wondering..
> 
> Because priority boosting doesn't help unless the callbacks also run
> RT priority.
> 
> I could make it so that they ran as normal tasks if !RCU_BOOST, but
> they would still need to run as RT tasks for RCU_BOOST.  I figured
> running them the same way in both cases would be simpler.

Ah, I thought you'd boost the threads along with the waiters, to the
same prio so that they wouldn't disturb higher priority tasks for no
reason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/