linux-kernel - RE: question on sched-rt group allocation cap: sched_rt_runtime

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1252249790.13541.28.camel@marge.simson.net>
Date:	Sun, 06 Sep 2009 17:09:50 +0200
From:	Mike Galbraith <efault@....de>
To:	Anirban Sinha <ASinha@...gmasystems.com>
Cc:	Lucas De Marchi <lucas.de.marchi@...il.com>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>, ani@...rban.org
Subject: RE: question on sched-rt group allocation cap: sched_rt_runtime_us

On Sun, 2009-09-06 at 07:53 -0700, Anirban Sinha wrote:
> 
> 
> 
> > Seems kjournald can end up depending on kblockd/3, which ain't
> > going anywhere with that 100% RT hog in the way,
> 
> I think in the past AKPM's response to this has been "just don't do
> it", i.e, don't hog the CPU with an RT thread.

Oh yeah, sure.  Best to run RT oinkers on isolated cpus.  It just
surprised me that the 100% compute RT cpu became involved in IO.

	-Mike

--
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/