Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@uni-koblenz.de>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: RedHat 5.0 RPMs for SGI...
Date: Sat, 10 Jan 1998 11:54:18 +0100	[thread overview]
Message-ID: <19980110115418.15445@thoma.uni-koblenz.de> (raw)
In-Reply-To: <Pine.LNX.3.95.980109192020.14617A-100000@lager.engsoc.carleton.ca>; from Alex deVries on Fri, Jan 09, 1998 at 07:25:50PM -0500

On Fri, Jan 09, 1998 at 07:25:50PM -0500, Alex deVries wrote:

> I had a closer look at it, and indeed, all the memory is accounted for.
> But, what I'm totally unused to is things taking up so much.  I've got
> 64MB in there now (although it's detected as 60248kB, it's missing 4MB).

The 60248kb is what the ARC firmware returns as free memory.

> Now I've got just the bare bones required to do anything productive:
> bdflush, inetd and a couple of shells.  There goes half my memory.
> 
> For example, 'su' takes up 4.5MB.  This seems like an awful lot to me,
> compared to the Intel equivalent of 1MB. I know the binaries are going to
> be larger because of the RISC thing, but really that large?
> 
> Is this normal?

It think the way these numbers are being computed is broken for MIPS.
MIPS executables are rougly 50-70% bigger than i386 ones; the size of the
data in executables and memory should be comparable.

  Ralf

  reply	other threads:[~1998-01-10 11:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-09 19:54 RedHat 5.0 RPMs for SGI Alex deVries
1998-01-09 20:07 ` Eric Kimminau
1998-01-10  0:25   ` Alex deVries
1998-01-10 10:54     ` Ralf Baechle [this message]
1998-01-10 18:17 ` Alan Cox
1998-01-10 18:17   ` Alan Cox
1998-01-10 18:39   ` ralf
1998-01-10 19:13   ` Alex deVries
  -- strict thread matches above, loose matches on Subject: below --
1998-01-10  1:21 Emmanuel Mogenet
1998-01-10 10:59 ` Ralf Baechle

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=19980110115418.15445@thoma.uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=adevries@engsoc.carleton.ca \
    --cc=linux@cthulhu.engr.sgi.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