mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: _deepfire@mail.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5 and lowmemory boxens
Date: Fri, 18 Oct 2002 12:54:15 +0100 (BST)	[thread overview]
Message-ID: <200210181154.g9IBsG2A001135@darkstar.example.net> (raw)
In-Reply-To: <E182V29-000Pfa-00@f15.mail.ru> from "Samium Gromoff" at Oct 18, 2002 03:11:13 PM

>    first: i`ve successfully ran 2.5.43 on a 386sx20/4M ram notebook.

Cool, I thought my 486sx20/4M was a good achievement :-)

>  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?).

I have found that 16450-based serial ports are unreliable under
2.5.x.  Enabling interrupt un-masking didn't help, and I suspect that
it is just the generally more bloated kernel making the cache, (or in
the case of a 386, the pre-fetch unit :-) ), less efficient, and
causing data to be lost.

>  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

Yes, I've noticed the same thing during my experiments with low-memory boxes.

>  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 am also very interested in it.

John.

  parent reply	other threads:[~2002-10-18 11:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 11:11 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
2002-10-18 11:54 ` jbradford [this message]
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=200210181154.g9IBsG2A001135@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=_deepfire@mail.ru \
    --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®