Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757048Ab2E3HXV (ORCPT ); Wed, 30 May 2012 03:23:21 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:48285 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756965Ab2E3HXT (ORCPT ); Wed, 30 May 2012 03:23:19 -0400 Date: Wed, 30 May 2012 09:23:13 +0200 From: Ingo Molnar To: Chen Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" , Joe Perches Subject: Re: [GIT PULL] x86/urgent fixes for v3.5 Message-ID: <20120530072313.GE2587@gmail.com> References: <20120523113432.GA12142@gmail.com> <4FBD1AC8.7020602@zytor.com> <20120523174844.GA3373@gmail.com> <4FBE5456.5020408@zytor.com> <20120524170715.GB21355@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1626 Lines: 49 * Chen wrote: > On Fri, May 25, 2012 at 1:07 AM, Ingo Molnar 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 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/