From: Ingo Molnar <mingo@kernel.org>
To: Chen <hi3766691@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Plumbers: Tweaking scheduler policy micro-conf RFP
Date: Wed, 23 May 2012 17:03:59 +0200 [thread overview]
Message-ID: <20120523150359.GB26974@gmail.com> (raw)
In-Reply-To: <CANQmPXhN92i9E8HqxE7pqz=kOwtn5Mz0crW37H6qs+XD420Yuw@mail.gmail.com>
* Chen <hi3766691@gmail.com> 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
next prev parent reply other threads:[~2012-05-23 15:04 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 16:16 Plumbers: Tweaking scheduler policy micro-conf RFP Vincent Guittot
2012-05-11 16:26 ` Steven Rostedt
2012-05-11 16:38 ` Vincent Guittot
2012-05-15 8:41 ` Juri Lelli
2012-05-15 0:53 ` Paul E. McKenney
2012-05-15 8:02 ` Vincent Guittot
2012-05-15 8:34 ` mou Chen
2012-05-15 9:07 ` Vincent Guittot
2012-05-15 9:17 ` Pantelis Antoniou
2012-05-15 10:28 ` Peter Zijlstra
2012-05-15 11:35 ` Pantelis Antoniou
2012-05-15 11:58 ` Peter Zijlstra
2012-05-15 12:32 ` Pantelis Antoniou
2012-05-15 12:59 ` Peter Zijlstra
2012-05-19 14:58 ` Luming Yu
2012-05-15 20:26 ` valdis.kletnieks
2012-05-15 20:33 ` Peter Zijlstra
2012-05-16 12:08 ` Pantelis Antoniou
2012-05-15 12:23 ` Peter Zijlstra
2012-05-15 12:27 ` Peter Zijlstra
2012-05-15 12:57 ` Vincent Guittot
2012-05-15 13:00 ` Peter Zijlstra
2012-05-15 15:05 ` Vincent Guittot
2012-05-15 15:19 ` Paul E. McKenney
2012-05-15 15:27 ` Vincent Guittot
2012-05-15 15:35 ` Peter Zijlstra
2012-05-15 15:45 ` Peter Zijlstra
2012-05-16 18:30 ` Peter Zijlstra
2012-05-19 17:08 ` Linus Torvalds
2012-05-19 22:55 ` Peter Zijlstra
2012-05-22 2:38 ` Chen
2012-05-22 5:14 ` Chen
2012-05-30 7:20 ` Ingo Molnar
2012-05-23 15:03 ` Ingo Molnar [this message]
2012-05-23 15:43 ` Joe Perches
2012-05-23 15:50 ` Ingo Molnar
2012-05-23 15:56 ` Joe Perches
2012-05-23 15:59 ` Ingo Molnar
2012-05-29 18:17 ` [PATCH] printk: Shrink printk_sched buffer size, eliminate it when !CONFIG_PRINTK Joe Perches
2012-06-05 16:04 ` Joe Perches
2012-06-06 7:25 ` Ingo Molnar
2012-06-06 7:33 ` Ingo Molnar
2012-06-06 7:42 ` Joe Perches
2012-05-19 23:13 ` Plumbers: Tweaking scheduler policy micro-conf RFP Peter Zijlstra
2012-05-19 23:22 ` Peter Zijlstra
2012-05-21 7:16 ` Ingo Molnar
2012-05-21 16:56 ` Linus Torvalds
2012-05-16 18:49 ` Vaidyanathan Srinivasan
2012-05-16 19:40 ` Peter Zijlstra
2012-05-16 21:20 ` Vincent Guittot
[not found] ` <20120518161817.GE18312@e103034-lin.cambridge.arm.com>
2012-05-18 16:24 ` Morten Rasmussen
2012-05-18 16:39 ` Peter Zijlstra
2012-05-18 16:46 ` Pantelis Antoniou
2012-05-15 16:30 ` Vaidyanathan Srinivasan
2012-05-15 18:13 ` Vincent Guittot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120523150359.GB26974@gmail.com \
--to=mingo@kernel.org \
--cc=hi3766691@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox