linux-kernel - Re: [PATCH] sched: properly account IRQ and RT load in SCHED

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]

Date:	Thu, 21 Aug 2008 13:40:40 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Nick Piggin <nickpiggin@...oo.com.au>,
	Gregory Haskins <ghaskins@...ell.com>,
	vatsa <vatsa@...ibm.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sched: properly account IRQ and RT load in SCHED_OTHER
	load balancing


* Peter Zijlstra <peterz@...radead.org> wrote:

> On Thu, 2008-08-21 at 13:17 +0200, Ingo Molnar wrote:
> > * Ingo Molnar <mingo@...e.hu> wrote:
> > 
> > > > This patch tries to solve this issue by accounting the time spend on 
> > > > both Real-Time tasks and IRQ handling, and using that to 
> > > > proportionally inflate the SCHED_OTHER load.
> > > 
> > > applied it to tip/sched/devel for more testing.
> > 
> > -tip testing found that it wouldnt build on UP in sched_debug.c - made 
> > that bit dependent on CONFIG_SMP. sched_scale_load() does not seem to be 
> > too meaningful on UP.
> 
> Thanks - just prior to posting I removed the empty stub for 
> sched_scale_load() because it didn't make sense for UP code to use 
> it...
> 
> So much for double checking myself.

hm, the empty stub might be useful still and would remove the #ifdef 
from sched_debug.c. Could you please send a delta patch against 
tip/master?

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