linux-kernel - Re: [GIT PULL] x86/urgent fixes for v3.5

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

Date:	Wed, 30 May 2012 09:23:13 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Chen <hi3766691@...il.com>
Cc:	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Joe Perches <joe@...ches.com>
Subject: Re: [GIT PULL] x86/urgent fixes for v3.5

* Chen <hi3766691@...il.com> wrote:

> On Fri, May 25, 2012 at 1:07 AM, Ingo Molnar <mingo@...nel.org> wrote:
> >
> > Interesting posts, first the "500K scheduler" nonsense now
> > printk nonsense?
> 
> printk nonsense?  You actually read my words wrong(LAUGH!)
> [I m going to quota my post]
>
> * Chen <hi3766691@...il.com> wrote:
> > Everyone knows that this patch had been unstable. Also, too
> > much code are pushed into printk() with the patch
>
> I mean that too much code are brought with the patch.

The 'Everyone knows that this patch had been unstable' bit is 
the nonsense.

> 500K scheduler is true. 248K(Core.c[MODULAR]) + 
> 148K(fair.c[CFS]) + 47K(rt.c[RT]) = 443K.(Does not include the 
> other source files of scheduler.) It is really a *HUGE* CPU 
> scheduler.[But it doesn't bring much advantages to desktop!!]

You are quite confused. Here's the reply I gave you in the other 
thread:

Only binary code is counted in bytes, source code is counted in 
lines.

20 KLOC for a full-featured CPU scheduler that does everything 
from simple UP scheduling to thousands of CPUs NUMA scheduling, 
cgroups, real-time and more, is entirely reasonable.

As a comparison the VM is 80+ KLOCS, arch/x86/ is 260+ KLOCs, 
networking is 720+ KLOCS and the FS subsystem is over 1 million 
lines of code.

The scheduler is in fact one of the smaller subsystems.

Thanks,

	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/