From: Andrew Morton <akpm@digeo.com>
To: Daniel Phillips <phillips@arcor.de>
Cc: Andi Kleen <ak@muc.de>, Samium Gromoff <_deepfire@mail.ru>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5 and lowmemory boxens
Date: Fri, 18 Oct 2002 15:37:03 -0700 [thread overview]
Message-ID: <3DB08D0F.331E5FDB@digeo.com> (raw)
In-Reply-To: E182ex9-0004yc-00@starship
Daniel Phillips wrote:
>
> On Friday 18 October 2002 18:50, Andrew Morton wrote:
> > > "Samium Gromoff" <_deepfire@mail.ru> writes:
> > > > first: i`ve successfully ran 2.5.43 on a 386sx20/4M ram notebook.
> >
> > ...
> >
> > timer.c and sched.c have significant NR_CPUS bloat problems on SMP.
> > Working on that.
>
> Oooh, yes! So 2.6 will be just fine for my smp dsl router...
>
Reducing NR_CPUS from 32 to 2 shrinks the ia32 kernel by 380 kilobytes.
Figure half a meg or more on 64-bit machines.
Not a huge amount. But not zero either.
next prev parent reply other threads:[~2002-10-18 22:31 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
2002-10-18 21:46 ` Daniel Phillips
2002-10-18 22:37 ` Andrew Morton [this message]
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=3DB08D0F.331E5FDB@digeo.com \
--to=akpm@digeo.com \
--cc=_deepfire@mail.ru \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
/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