Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758298Ab2EYCke (ORCPT ); Thu, 24 May 2012 22:40:34 -0400 Received: from mail-ob0-f174.google.com ([209.85.214.174]:58510 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751960Ab2EYCkd (ORCPT ); Thu, 24 May 2012 22:40:33 -0400 MIME-Version: 1.0 In-Reply-To: <20120524170715.GB21355@gmail.com> References: <20120523113432.GA12142@gmail.com> <4FBD1AC8.7020602@zytor.com> <20120523174844.GA3373@gmail.com> <4FBE5456.5020408@zytor.com> <20120524170715.GB21355@gmail.com> Date: Fri, 25 May 2012 10:40:32 +0800 Message-ID: Subject: Re: [GIT PULL] x86/urgent fixes for v3.5 From: Chen To: Ingo Molnar Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" , Joe Perches Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 928 Lines: 22 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. 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!!] -- 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/