From: Christoph Rohland <cr@sap.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@transmeta.com (Linus Torvalds),
viro@math.psu.edu (Alexander Viro),
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rootfs (part 1)
Date: 17 May 2001 08:46:11 +0200 [thread overview]
Message-ID: <m34ruk5v7w.fsf@linux.local> (raw)
In-Reply-To: <E150B2Z-0004fV-00@the-village.bc.nu>
In-Reply-To: <E150B2Z-0004fV-00@the-village.bc.nu>
Hi Alan,
On Thu, 17 May 2001, Alan Cox wrote:
> I think you have a major tool problem.
>
> bash-2.04$ size mm/shmem.o
> text data bss dec hex filename
> 7422 572 0 7994 1f3a mm/shmem.o
> bash-2.04$ size fs/ramfs/ramfs.o
> text data bss dec hex filename
> 3185 368 0 3553 de1 fs/ramfs/ramfs.o
>
> Never trust ls -l size for binaries, its very very unrelated.
>
> So ramfs is 3553 bytes, shmem.o in total is 8K on current -ac.
But you cannot disable shmem.o totally. That's my whole point in the
discussion. Why add something what is mostly included in the kernel
already?
You have to compare shmem with tmpfs against shmem w/o it:
text data bss dec hex filename
3398 376 0 3774 ebe fs/ramfs/ramfs.o
5150 484 0 5634 1602 mm/shmem.o
9174 636 0 9810 2652 mm/shmem.o+tmpfs
So tmpfs is 400 Bytes bigger than ramfs.
If you add the correct timestamp handling the difference will go down
further. And we gain functionality, don't we?
Greetings
Christoph
next prev parent reply other threads:[~2001-05-17 6:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-16 12:12 [PATCH] rootfs (part 1) 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
2001-05-16 18:33 ` Alexander Viro
2001-05-16 23:49 ` Alan Cox
2001-05-17 6:46 ` Christoph Rohland [this message]
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=m34ruk5v7w.fsf@linux.local \
--to=cr@sap.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.