Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965101Ab2EWPEM (ORCPT ); Wed, 23 May 2012 11:04:12 -0400 Received: from mail-ee0-f46.google.com ([74.125.83.46]:61283 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964888Ab2EWPEF (ORCPT ); Wed, 23 May 2012 11:04:05 -0400 Date: Wed, 23 May 2012 17:03:59 +0200 From: Ingo Molnar To: Chen Cc: Peter Zijlstra , Vincent Guittot , torvalds@linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: Plumbers: Tweaking scheduler policy micro-conf RFP Message-ID: <20120523150359.GB26974@gmail.com> References: <1337084609.27020.156.camel@laptop> <1337086834.27020.162.camel@laptop> <1337096141.27694.82.camel@twins> <1337193010.27694.146.camel@twins> <1337468148.573.139.camel@twins> 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: 1033 Lines: 33 * Chen wrote: > Still you are just trying to said that your code is not bloated? > Up to over 500K for a cpu scheduler. Laughing Where did you get that 500K from? You are off from the truth almost by an order of magnitude. Here's the scheduler size on Linus's latest tree, on 64-bit defconfig's: $ size kernel/sched/built-in.o text data bss dec hex filename 83611 10404 2524 96539 1791b kernel/sched/built-in.o That's SMP+NUMA, i.e. everything included. The !NUMA !SMP UP scheduler, if you are on a size starved ultra-embedded device, is even smaller, just 22K: $ size kernel/sched/built-in.o text data bss dec hex filename 19882 2218 148 22248 56e8 kernel/sched/built-in.o 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/