linux-kernel - Re: sched_yield: delete sysctl_sched_compat

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071203220559.GA11906@elte.hu>
Date:	Mon, 3 Dec 2007 23:05:59 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mark Lord <lkml@....ca>
Cc:	Chris Friesen <cfriesen@...tel.com>, davids@...master.com,
	Nick Piggin <nickpiggin@...oo.com.au>,
	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: sched_yield: delete sysctl_sched_compat_yield


* Mark Lord <lkml@....ca> wrote:

> Ack.  And what of the suggestion to try to ensure that a yielding task 
> simply not end up as the very next one chosen to run?  Maybe by 
> swapping it with another (adjacent?) task in the tree if it comes out 
> on top again?

we did that too for quite some time in CFS - it was found to be "not 
agressive enough" by some folks and "too agressive" by others. Then when 
people started bickering over this we added these two simple corner 
cases - switchable via a flag. (minimum agression and maximum agression)

> (I really don't know the proper terminology to use here, but hopefully 
> Ingo can translate that).

the terminology you used is perfectly fine.

> Thanks Ingo -- I *really* like this scheduler!

heh, thanks :) For which workload does it make the biggest difference 
for you? (and compared to what other scheduler you used before? 2.6.22?)

	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/