public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@uni-koblenz.de>
To: "Vilain, Sam" <sam.vilain@nz.unisys.com>
Cc: "'Jim Mostek'" <mostek@sgi.com>, linux-kernel@vger.rutgers.edu
Subject: Re: XFS and journalling filesystems
Date: Mon, 31 May 1999 04:14:37 +0200	[thread overview]
Message-ID: <19990531041437.C672@uni-koblenz.de> (raw)
In-Reply-To: <76D8782817C5D211A37400104B0C84B029C52F@nz-wlg-exch-1.nz.unisys.com>; from Vilain, Sam on Sat, May 29, 1999 at 06:48:19AM -0400

On Sat, May 29, 1999 at 06:48:19AM -0400, Vilain, Sam wrote:

> As a dangerous rule of thumb, LOC ~ code size.  More code size = bigger
> kernel = less (buffercache|user memory).  <flamesuit>This is a fear of Linux
> kernel developers - Linux ending up as slow as say, Solaris on low end
> machines (even if it kicks butt on 6144-way SMP).</flamesuit>

Nobody builds 6144-way SMPs, not Sun nor somebody else.  The SMP paradigm
just doesn't scale that far.

> Numbers are often good in arguments like this.  ie, how big is the ext2fs
> module under Linux/MIPS, compared to the xfs module under Irix?  [Comparing
> with Linux/i386 should probably be avoided, because i386 code is (generally)
> more instructions/word, even if you need a few extra million transistors to
> decode it :)].

[ralf@lappi linux-sgi]$ mips-linux-size fs/ext2/ext2.o
   text	   data	    bss	    dec	    hex	filename
  60080	    496	   1024	  61600	   f0a0	fs/ext2/ext2.o
[ralf@lappi linux-sgi]$ 

The archive /usr/cpu/sysgen/IP22boot/xfs.a of IRIX 6.2 has in total a
.text size of 274864.  That's 32 bit code btw.

  Ralf

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

       reply	other threads:[~1999-05-31  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <76D8782817C5D211A37400104B0C84B029C52F@nz-wlg-exch-1.nz.unisys.com>
1999-05-31  2:14 ` Ralf Baechle [this message]
     [not found] ` <3753A4A5.C2A4FE91@engr.sgi.com>
     [not found]   ` <199906010928.CAA04308@pizda.davem.net>
1999-06-01 10:15     ` XFS and journalling filesystems Dan Koren
     [not found] <199905281653.LAA61598@fsgi344.cray.com>
     [not found] ` <012201bea93f$db9d1050$e6976dcf@TRGMERKEYNT2000>
1999-05-31 23:17   ` Stephen C. Tweedie
     [not found] <E10m0gq-0000pk-00@the-village.bc.nu>
1999-05-27 19:11 ` Dan Koren

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=19990531041437.C672@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=mostek@sgi.com \
    --cc=sam.vilain@nz.unisys.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