linux-kernel - Re: [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2

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: <1173731811.6431.48.camel@Homer.simpson.net>
Date:	Mon, 12 Mar 2007 21:36:51 +0100
From:	Mike Galbraith <efault@....de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Con Kolivas <kernel@...ivas.org>, Ingo Molnar <mingo@...e.hu>,
	linux kernel mailing list <linux-kernel@...r.kernel.org>,
	ck list <ck@....kolivas.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2

On Mon, 2007-03-12 at 08:26 -0700, Linus Torvalds wrote:
> 
> On Mon, 12 Mar 2007, Mike Galbraith wrote:
> >
> > On Mon, 2007-03-12 at 22:23 +1100, Con Kolivas wrote:
> > 
> > > Mike the cpu is being proportioned out perfectly according to fairness as I 
> > > mentioned in the prior email, yet X is getting the lower latency scheduling. 
> > > I'm not sure within the bounds of fairness what more would you have happen to 
> > > your liking with this test case?
> > 
> > It has been said that "perfection is the enemy of good".  The two
> > interactive tasks receiving 40% cpu while two niced background jobs
> > receive 60% may well be perfect, but it's damn sure not good.
> 
> Well, the real problem is really "server that works on behalf of somebody 
> else".

Yes, exactly.  We have a disconnect.  The process consists of both.  If
either client or server doesn't get enough, the process is a failure.

> X is just the worst *practical* example of this, since not only is it the 
> most common such server, it's also a case where people see interactive 
> issues really easily.
> 
> And the problem is that a lot of clients actually end up doing *more* in 
> the X server than they do themselves directly. Doing things like showing a 
> line of text on the screen is a lot more expensive than just keeping track 
> of that line of text, so you end up with the X server easily being marked 
> as getting "too much" CPU time, and the clients as being starved for CPU 
> time. And then you get bad interactive behaviour.
> 
> So "good fairness" really should involve some notion of "work done for 
> others". It's just not very easy to do..

Purely from the interactivity side, I connected via a simple tag X as
TASK_INTERACTIVE thingy, and boosted the tasks it was waking.  Worked
for things like the heavy cpu visualizations while other things are
going on in the background.  It was full of evilness though.

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