From: Anton Blanchard <anton@samba.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 23:59:19 +1100 [thread overview]
Message-ID: <20011219125919.GD24009@krispykreme> (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>
> 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.
Check out all the cacheline_aligned usage, in all the cases I could see
there was no reason to do this on a UP machine. You could probably get
away with redefining them to do nothing.
Also you could drop the sizes of the hashes (dentry, inode, mount,
buffer, page, route) if they are taking up RAM.
Anton
next prev parent reply other threads:[~2001-12-19 13:00 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 [this message]
2001-12-19 13:03 ` David Woodhouse
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=20011219125919.GD24009@krispykreme \
--to=anton@samba.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