public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Johansson <ken@canit.se>
To: root@chaos.analogic.com
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>, linux-kernel@vger.kernel.org
Subject: Re: kernel size
Date: Wed, 10 Oct 2001 03:30:03 +0200	[thread overview]
Message-ID: <3BC3A49B.15D1997C@canit.se> (raw)
In-Reply-To: <Pine.LNX.3.95.1011009114946.4152A-100000@chaos.analogic.com>

"Richard B. Johnson" wrote:

> On Tue, 9 Oct 2001, Horst von Brand wrote:
>
> > "Richard B. Johnson" <root@chaos.analogic.com> said:
> > > On Tue, 9 Oct 2001, Ingo Oeser wrote:
> >
> > [...]
> >
> > > > strip -R .ident -R .comment -R .note
> > > >
> > > > is your friend.
> >
> > [...]
> >
> > > Yes! Wonderful...
> > > -rwxr-xr-x   1 root     root      1571516 Oct  9 10:50 vmlinux
> > > -rwxr-xr-x   1 root     root      1590692 Oct  1 13:26 vmlinux.OLD
> > >
> > > That got rid of some cruft.
> >
> > Yep. A WHOOPing 1.2% of the total. BTW, is this stuff ever being loaded
> > into RAM with the executable kernel, discarded on boot, or what?
> >
>
> Yes. It shows in /proc/kcore. Just wasted. It does mean something
> on an embedded system.
>
> It just __might__ mean that I can use a later kernel than 2.4.1
> (they grow, you know). I'm mucking with things now.
>

You do know that kcore shows all memory not just what was compiled into the
kernel. even usless old file cache so it's not so easy to se how much space
the strings use of real memory.

Test with creating a file with a string your not likly to have anywhere else.

num=1 ;while ((1)) ; do echo "xenomorph $num"; num=$(($num+1)) ; done >1.txt

strings /proc/kcore | grep xenomorph



  parent reply	other threads:[~2001-10-10  1:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-09 14:16 kernel size VDA
2001-10-09 13:26 ` [solid]
2001-10-09 13:28 ` Nikita Danilov
2001-10-10  9:10   ` kernel size, kcore fun Helge Hafting
2001-10-09 14:16 ` kernel size Richard B. Johnson
2001-10-09 14:43   ` Ingo Oeser
2001-10-09 14:52     ` Richard B. Johnson
2001-10-09 15:43       ` Horst von Brand
2001-10-09 15:53         ` Richard B. Johnson
2001-10-10  1:29           ` Keith Owens
2001-10-10 13:00             ` Richard B. Johnson
2001-10-10 14:47               ` vda
2001-10-11 12:41                 ` vda
2001-10-10  1:30           ` Kenneth Johansson [this message]
2001-10-09 15:55         ` Jakub Jelinek
2001-10-10  1:27     ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2001-12-13  4:38 Kernel size rohit prasad
2001-12-07  8:53 kernel size rohit prasad
2001-12-07 16:46 ` Eli Carter
2001-10-04 13:11 Security question: "Text file busy" overwriting executables but not shared libraries? Eric W. Biederman
2001-10-04 14:24 ` Kernel size Richard B. Johnson
2001-10-13 20:35   ` Aaron Lehmann

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=3BC3A49B.15D1997C@canit.se \
    --to=ken@canit.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=vonbrand@inf.utfsm.cl \
    /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