mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipv4: only produce one record in fib_seq_show
Date: Sun, 20 Oct 2002 17:08:05 +1000	[thread overview]
Message-ID: <22353.1035097685@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 20 Oct 2002 02:08:49 -0300." <20021020050849.GD15254@conectiva.com.br>

On Sun, 20 Oct 2002 02:08:49 -0300, 
Arnaldo Carvalho de Melo <acme@conectiva.com.br> wrote:
>CONFIG_PROC_FS=y
>[acme@oops net-2.5]$ l net/ipv4/built-in.o
>-rw-rw-r--    1 acme     acme       328783 Out 20 01:44 net/ipv4/built-in.o
>
>CONFIG_PROC_FS=n
>[acme@oops net-2.5]$ l net/ipv4/built-in.o
>-rw-rw-r--    1 acme     acme       320708 Out 20 02:03 net/ipv4/built-in.o

The size of an object on disk is misleading, it contains comments,
notes, relocations, debug sections etc. which are discarded when
vmlinux is built, as well as init sections which are reused after the
kernel has booted.  Also the on disk size completely excludes bss, the
bss area is created and zeroed at load time.  ls -l on a kernel object
is not a good test, use size -A instead.  On a 2.4.19 system :-

# ls -l net/ipv4/ipv4.o
-rw-r--r--    1 kaos     ocs        338885 Sep 29 13:59 net/ipv4/ipv4.o

# size -A net/ipv4/ipv4.o 
net/ipv4/ipv4.o  :
section                     size   addr
.text                     216368      0
.text.init                  2784      0   reused after boot
.fixup                       411      0
.rodata                     1442      0
.rodata.str1.32            13280      0
.rodata.str1.1              2992      0
__ex_table                   288      0
.data                      11024      0
.data.cacheline_aligned      192      0
.initcall.init                 4      0   reused after boot
.bss                       46464      0   not on disk, but occupies kernel space
.comment                    1815      0   not loaded into the kernel
.note                        660      0   not loaded into the kernel
Total                     297724          misleading!


  parent reply	other threads:[~2002-10-20  7:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-19 23:32 Arnaldo Carvalho de Melo
2002-10-19 23:54 ` David S. Miller
2002-10-20  0:09   ` Arnaldo Carvalho de Melo
2002-10-20  0:38     ` David S. Miller
2002-10-20  1:03       ` Arnaldo Carvalho de Melo
2002-10-20  4:13         ` David S. Miller
2002-10-20  5:08           ` Arnaldo Carvalho de Melo
2002-10-20  5:14             ` David S. Miller
2002-10-20  5:26               ` Arnaldo Carvalho de Melo
2002-10-20  5:52               ` Andrew Morton
2002-10-20  5:15             ` David S. Miller
2002-10-20  5:30               ` Arnaldo Carvalho de Melo
2002-10-20  7:08             ` Keith Owens [this message]
     [not found] <20021020010331.GB15254@conectiva.com.br.suse.lists.linux.kernel>
     [not found] ` <20021019.211307.00017347.davem@redhat.com.suse.lists.linux.kernel>
     [not found]   ` <20021020050849.GD15254@conectiva.com.br.suse.lists.linux.kernel>
     [not found]     ` <20021019.221403.116117803.davem@redhat.com.suse.lists.linux.kernel>
2002-10-20  5:58       ` Andi Kleen

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=22353.1035097685@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®