All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Andi Kleen <ak@muc.de>
Cc: Samium Gromoff <_deepfire@mail.ru>, linux-kernel@vger.kernel.org
Subject: Re: 2.5 and lowmemory boxens
Date: Fri, 18 Oct 2002 09:50:17 -0700	[thread overview]
Message-ID: <3DB03BC9.F2986C53@digeo.com> (raw)
In-Reply-To: m37kggyo7r.fsf@averell.firstfloor.org

Andi Kleen wrote:
> 
> "Samium Gromoff" <_deepfire@mail.ru> writes:
> 
> >    first: i`ve successfully ran 2.5.43 on a 386sx20/4M ram notebook.
> >
> >  the one problem was the ppp over serial not working, but i suspect
> >  that it just needs to be recompiled with 2.5 headers (am i right?).
> >
> >  the other was, well, the fact that ultra-stripped 2.5.43
> >  still used 200k more memory than 2.4.19, and thats despite it was
> >  compiled with -Os instead of -O2.
> >  actually it was 2000k free with 2.4 vs 1800k  free with 2.5
> >
> >  i know Rik had plans of some ultra bloody embedded/lowmem
> >  changes for such cases. i`d like to hear about things in the area :)
> 
> I would start with clamping down all the hash tables.

Well here's some low-hanging fruit:

mnm:/usr/src/25> size kernel/pid.o
   text    data     bss     dec     hex filename
   1677    1088  131104  133869   20aed kernel/pid.o

(I have a trollpatch to fix this)

And the radix_tree_node mempool is 140k; I plan to do away with
that altogether.

timer.c and sched.c have significant NR_CPUS bloat problems on SMP.
Working on that.

  reply	other threads:[~2002-10-18 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 11:11 2.5 and lowmemory boxens Samium Gromoff
2002-10-18 11:35 ` Andi Kleen
2002-10-18 16:50   ` Andrew Morton [this message]
2002-10-18 21:46     ` Daniel Phillips
2002-10-18 22:37       ` Andrew Morton
2002-10-18 11:54 ` jbradford
2002-10-18 14:21   ` Russell King

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=3DB03BC9.F2986C53@digeo.com \
    --to=akpm@digeo.com \
    --cc=_deepfire@mail.ru \
    --cc=ak@muc.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.