linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: Andi Kleen <ak@muc.de>, Petr Dusil <pdusil@razdva.cz>,
	linux-mm@kvack.org
Subject: Re: Reduce Linux memory requirements for an Embedded PC
Date: Sat, 24 Mar 2001 14:31:35 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0103241427110.1863-100000@imladris.rielhome.conectiva> (raw)
In-Reply-To: <20010324175627.F26121@nightmaster.csn.tu-chemnitz.de>

On Sat, 24 Mar 2001, Ingo Oeser wrote:
> On Sat, Mar 24, 2001 at 01:21:29PM -0300, Rik van Riel wrote:
> > I'm willing to work on a CONFIG_TINY option for 2.5 which
> > does things like this (but I'll have to finish some VM
> > things first ;)).
> 
> Why not 2.4? It is only a configuration thing, right? People are
> using Linux more and more for embedded stuff. So waiting 2 years
> more is not an option.

It depends.  I definately want to start development on 2.4
and keep some patch around. If things turn out to be trivial
we can submit the patch for 2.4, if not we can keep the
patch separately.

> I'm willing to help, if we collect some ideas on WHAT to do
> first.

- write a script to move all extern inline functions to
  a C file and have them compile out-of-line
- drastically reduce (or even abolish) hash tables for
  buffer cache, page cache, network routing, sockets, ...
  [ if you have 20 items, you may as well walk a list ]
- compile out all kinds of code which make optimisations
  that only work for larger machines (dynamic readahead
  size reduction, ...)

> Autotuning is nice, but has always the chance to fail for corner
> cases. Taking these into account to generates too much code
> bloat. So making the required tunables available (as already
> happend with threads-max, file-max and the like) is supporting
> the idea of 'providing features, not policy'.

*nod*

regards,

Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

		http://www.surriel.com/
http://www.conectiva.com/	http://distro.conectiva.com.br/

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  reply	other threads:[~2001-03-24 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-24  9:59 Petr Dusil
2001-03-24 12:39 ` Andi Kleen
2001-03-24 16:21   ` Rik van Riel
2001-03-24 16:56     ` Ingo Oeser
2001-03-24 17:31       ` Rik van Riel [this message]
2001-03-24 19:06     ` Andrew Morton
2001-03-24 15:23 ` Stephen C. Tweedie

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=Pine.LNX.4.21.0103241427110.1863-100000@imladris.rielhome.conectiva \
    --to=riel@conectiva.com.br \
    --cc=ak@muc.de \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-mm@kvack.org \
    --cc=pdusil@razdva.cz \
    /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