LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@gmx.de>
To: Chris Friesen <cfriesen@nortel.com>
Cc: Bodo Eggert <7eggert@gmx.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-kernel@vger.kernel.org, jeffschroeder@computer.org
Subject: Re: [PATCH] use tmpfs for rootfs v2
Date: Fri, 17 Oct 2008 00:45:22 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.0.999.0810170025090.14480@be1.lrz> (raw)
In-Reply-To: <48F7A971.3040500@nortel.com>

On Thu, 16 Oct 2008, Chris Friesen wrote:
> Bodo Eggert wrote:

> > Having tmpfs as the root filesystem allows you to get rid of the now unused
> > ramfs and free some kernel memory. On my system, that's about 5198 bytes
> > compared to having a ramfs root.
> 
> If you're not using swap, I assume the memory usage of tmpfs and ramfs would
> be identical?

I'd rather think having ACL, security labels etc. pp. will make tmpfs use 
more memory per file or directory. If you have no use for tmpfs' features,
you should use ramfs. But if you do want to use tmpfs in your system,
my guess is you'll be most likely be better off using no ramfs.
-- 
Good programming is 99% sweat and 1% coffee.

  reply	other threads:[~2008-10-16 22:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 12:03 [PATCH] use tmpfs for rootfs Bodo Eggert
2008-10-16 13:10 ` Geert Uytterhoeven
2008-10-16 17:35   ` Bodo Eggert
2008-10-16 17:39   ` [PATCH] use tmpfs for rootfs v2 Bodo Eggert
2008-10-16 20:52     ` Chris Friesen
2008-10-16 22:45       ` Bodo Eggert [this message]
2008-10-16 21:03     ` Jeff Schroeder
2008-10-16 22:53       ` Bodo Eggert
2008-10-17 11:16       ` [PATCH] use tmpfs for rootfs v3 Bodo Eggert
2008-10-19 18:12         ` Mike Frysinger
2008-10-20 18:13           ` Bodo Eggert
2008-10-22 19:03             ` Mike Frysinger

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=alpine.LSU.0.999.0810170025090.14480@be1.lrz \
    --to=7eggert@gmx.de \
    --cc=cfriesen@nortel.com \
    --cc=geert@linux-m68k.org \
    --cc=jeffschroeder@computer.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] use tmpfs for rootfs v2' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).