linux-kernel - Re: [ck] Re: Linus 2.6.23-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]

Date:	Sat, 28 Jul 2007 14:09:46 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Diego Calleja <diegocg@...il.com>
cc:	Jan Engelhardt <jengelh@...putergmbh.de>,
	Jonathan Jessup <jonathanjessup@...il.com>,
	Grzegorz Kulewski <kangur@...com.net>,
	linux-kernel@...r.kernel.org, ck@....kolivas.org, lkml@...anurb.dk
Subject: Re: [ck] Re: Linus 2.6.23-rc1

On Sat, 28 Jul 2007, Diego Calleja wrote:

> El Sat, 28 Jul 2007 11:05:25 -0700 (PDT), Linus Torvalds <torvalds@...ux-foundation.org> escribió:
> > 
> > So "modal" things are good for fixing behaviour in the short run. But they 
> > are a total disaster in the long run, and even in the short run they tend 
> > to have problems (simply because there will be cases that straddle the 
> > line, and show some of _both_ issues, and now *neither* mode is the right 
> > one)
> 
> I fully agree with this, but plugsched could have avoided this useless "division"
> on the topic of SD vs CFS. IMO that counts as an advantage, too ;)

Sure. I actually think it's a huge advantage (see the ManagementStyle file 
on pissing people off), but at the same time, I don't like playing 
politics with technology. The kernel is a technical project, and I make 
technical decisions.

So I absolutely detest adding code for "political" reasons.

I personally feel that modal behaviour is bad, so it would introduce what 
is in my opinion bad code, and likely result in problems not being found 
and fixed as well (because people would pick the thing that "works for 
them", and ignore the problems in the other module). So while I don't like 
making irreversible decisions (and the choice of CFS wasn't irreversible 
in itself, but if it pisses off Con, _that_ is generally not reversible), 
I dislike even more making a half-assed decision.

So rather than making a choice at all, my other choice would have been to 
not merge _either_ scheduler, and let people just continue to fight it 
out. Would that have made people happier? I seriously doubt it.

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