public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Marko Kenttälä" <marko.kenttala@teraflops.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel memory usage optimisations?
Date: Wed, 19 Dec 2001 13:03:32 +0000	[thread overview]
Message-ID: <7603.1008767012@redhat.com> (raw)
In-Reply-To: <5.1.0.14.2.20011219144636.03498a10@mail.teraflops.com>
In-Reply-To: <5.1.0.14.2.20011219144636.03498a10@mail.teraflops.com>


marko.kenttala@teraflops.com said:
>  I understand that best area for saving memory usage is the C-library
> but  are there any other kernel areas? I'm thinking of dropping
> swapfile support  and maybe some other subsystems that are not needed
> in embedded device. 

You could potentially remove block device support altogether.

--
dwmw2



      parent reply	other threads:[~2001-12-19 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 12:48 Kernel memory usage optimisations? Marko Kenttälä
2001-12-19 12:59 ` Anton Blanchard
2001-12-19 13:03 ` David Woodhouse [this message]

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=7603.1008767012@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marko.kenttala@teraflops.com \
    /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