From: Oleg Verych <olecom@flower.upol.cz>
To: Ingo Molnar <mingo@elte.hu>
Cc: "T. J. Brumfield" <enderandrew@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: about modularization
Date: Sun, 2 Sep 2007 00:02:22 +0200 [thread overview]
Message-ID: <E1IRb2s-0001Qp-5j@flower> (raw)
In-Reply-To: <20070803131900.GA26203@elte.hu>
* Date: Fri, 3 Aug 2007 15:19:00 +0200
* Received-SPF: softfail (mx3: transitioning domain of elte.hu does not designate 157.181.1.14 as permitted sender) client-ip=157.181.1.14; envelope-from=mingo@elte.hu; helo=elvis.elte.hu;
> If you boot into a distro kernel on
> a typical PC, about half of the kernel code that the box runs in any
> moment will be in modules, half of it is in the "kernel core". For
> example, on a random laptop:
That was your laptop and distro.
> $ echo `lsmod | cut -c1-30 | cut -d' ' -f2-` | sed 's/Size //' |
> sed 's/ /+/g' | bc
> 2513784
>
> i.e. 2.5 MB of modules. The core kernel's size:
>
> $ dmesg | grep 'kernel code'
> Memory: 2053212k/2087808k available (2185k kernel code, 33240k reserved, 1174k data, 244k init, 1170304k highmem)
>
> 2.1 MB of kernel core code. (of course the total body of "possible
> drivers" is 10 times larger than that of the core kernel - but the
> fundamental 'variety' is not.)
Just for reference here's my 2+ years old Asus A4K, kernel is form
Debian Etch:
deen:/tmp# uname -a
Linux deen 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 x86_64
deen:/tmp# lsmod | (read a; while read a b c; do S=$((b+${S=0})); done; echo $S)
1583684
deen:/tmp# lsmod | grep xfs
xfs 485192 3
deen:/tmp# dmesg | grep kernel\ code
Memory: 506676k/523520k available (1930k kernel code, 16456k reserved, 868k data, 176k init)
Apart from diff in hardware and implied designing/coding skills, decision
was made
* after one "wrong" response plus illness from Con,
* brave core-duo by Ingo and Tomas, who made some bunch of students to test
scheduler and reported success to Linus.
I don't know why, after all that variety of things (mostly drivers, but
recent *fd also) there's such big resistance to anything that's useful
and used by ordinary people. A star sickness, pride? If yes, that's just
ridiculous, but who cares.
____
next prev parent reply other threads:[~2007-09-01 21:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 12:07 Scheduler Situation T. J. Brumfield
2007-08-03 12:31 ` Alistair John Strachan
2007-08-03 12:52 ` Oleksandr Natalenko
[not found] ` <192840a00708030616g22d9dd16o95b2620bfe3347a8@mail.gmail.com>
2007-08-03 13:27 ` Андрій Мішковський
2007-08-03 13:45 ` Alistair John Strachan
2007-08-03 13:00 ` debian developer
2007-08-03 15:28 ` about modularization Ingo Molnar
2007-08-03 13:19 ` Ingo Molnar
[not found] ` <cdc89fe60708030651s54b5f0e0j938450632cf621c5@mail.gmail.com>
2007-08-03 13:52 ` Fwd: " T. J. Brumfield
2007-08-03 15:02 ` Ingo Molnar
2007-08-03 15:13 ` Ingo Molnar
2007-08-03 17:47 ` Rene Herman
2007-08-03 18:59 ` Ingo Molnar
2007-09-01 22:02 ` Oleg Verych [this message]
[not found] ` <200708031354.15485.alistair@devzero.co.uk>
[not found] ` <cdc89fe60708030712q391de609o3999a870ea7cbcbd@mail.gmail.com>
[not found] ` <200708031540.29687.alistair@devzero.co.uk>
2007-08-03 14:51 ` Scheduler Situation T. J. Brumfield
2007-08-03 15:05 ` Alistair John Strachan
-- strict thread matches above, loose matches on Subject: below --
2007-08-06 20:20 about modularization Mitchell Erblich
2007-08-06 20:50 ` Rene Herman
2007-08-06 21:48 Mitchell Erblich
2007-08-06 23:35 ` Rene Herman
2007-08-06 23:45 ` Rene Herman
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=E1IRb2s-0001Qp-5j@flower \
--to=olecom@flower.upol.cz \
--cc=enderandrew@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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