mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rootfs (part 1)
Date: 16 May 2001 20:46:46 +0200	[thread overview]
Message-ID: <m3itj15dyh.fsf@linux.local> (raw)
In-Reply-To: <Pine.LNX.4.21.0105161055270.4738-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.21.0105161055270.4738-100000@penguin.transmeta.com>

Hi Linus,

On Wed, 16 May 2001, Linus Torvalds wrote:
> 
> On 16 May 2001, Christoph Rohland wrote:
>> 
>> cr:/speicher/src/u4ac9 $ ls -l mm/shmem.o*
>> -rw-r--r--    1 cr       users      154652 Mai 16 19:27 mm/shmem.o-tmpfs
>> -rw-r--r--    1 cr       users      180764 Mai 16 19:24 mm/shmem.o+tmpfs
>> cr:/speicher/src/u4ac9 $ ls -l fs/ramfs/ramfs.o
>> -rw-r--r--    1 cr       users      141452 Mai 16 19:27 fs/ramfs/ramfs.o
>> 
>> So CONFIG_TMPFS adds 26k and ramfs 140k.
> 
> What the hell are you doing? Compiling with debugging or something?

Yep, sorry that was uml with debugging info.

> The ramfs inode.o file (the only file that ramfs contains) has 376
> bytes of data and 1612 bytes of code. BYTES. The whole final object
> file with all the relocation information is
> 
> 	-rw-r--r-- 1 torvalds eng 5734 May 16 10:58 ramfs.o
> 
> but out of that 5.5kB, only 2kB are actually linked into the kernel
> and are used to _run_.

-rw-r--r--    1 root     root         8656 May 16 20:27 fs/ramfs/ramfs.o
-rw-r--r--    1 root     root        11688 May 16 20:24 mm/shmem.o-tmpfs
-rw-r--r--    1 root     root        18592 May 16 20:20 mm/shmem.o+tmpfs

That's an -ac kernel, so ramfs does accounting and is a little bigger
than yours.

So the read/write support in tmpfs is about the same size as ramfs.

Greetings
		Christoph



  parent reply	other threads:[~2001-05-16 18:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-16 12:12 Alexander Viro
2001-05-16 14:43 ` Christoph Rohland
2001-05-16 18:23   ` Alexander Viro
2001-05-16 19:47     ` Christoph Rohland
2001-05-16 23:37   ` Alan Cox
2001-05-16 17:11 ` Linus Torvalds
2001-05-16 17:45   ` Christoph Rohland
2001-05-16 17:55     ` Jeff Garzik
2001-05-16 18:00     ` Linus Torvalds
2001-05-16 18:23       ` David L. Parsley
2001-05-16 18:46       ` Christoph Rohland [this message]
2001-05-16 18:33     ` Alexander Viro
2001-05-16 23:49     ` Alan Cox
2001-05-17  6:46       ` Christoph Rohland
2001-05-16 18:48   ` Alexander Viro
2001-05-16 22:21     ` H. Peter Anvin
2001-05-16 23:06       ` Alexander Viro
2001-05-16 23:24         ` H. Peter Anvin
2001-05-16 23:31           ` Alexander Viro
2001-05-16 23:33 ` Alan Cox
2001-05-17  0:10   ` Alexander Viro

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=m3itj15dyh.fsf@linux.local \
    --to=cr@sap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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®