linux-kernel - Re: [patch] sched_clock(): cleanups, #2

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:	Fri, 25 May 2007 12:45:36 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Andi Kleen <andi@...stfloor.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Satyam Sharma <satyam.sharma@...il.com>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [patch] sched_clock(): cleanups, #2

On Fri, 25 May 2007, Ingo Molnar wrote:
> 
> sure enough, i'll work something sane out - i already have it partly 
> split up. It will probably be something along the lines of: 'remove 
> stuff that we can remove and still have functional scheduling' followed 
> by an 'add minimal CFS patch' and then nicely split up 'CFS related 
> add-ons' (like the task-stats accounting things, debugging, etc).

Ok, that sounds good. Some of that is obviously already in separate files 
already, even if they then just get #include'd into the main sched.c, so 
yeah, splitting it up along those lines makes sense.

> Do you think i should try to split up the core CFS bits some more beyond 
> this level? (that would be quite nontrivial i suspect)

I'd love to see some of that too, but I suspect that with something like 
the scheduler, it's hard to have any reasonable (and working!) points that 
make much sense. At some point, the changes to make it work incrementally 
get bigger than the patches themselves, and rather than show what's going 
on, it might _hide_ what's going on.

		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/