From: Mike McDonald <mikemac@titian.engr.sgi.com>
To: linux@cthulhu.engr.sgi.com
Subject: How big is the Linux/MIPS kernel?
Date: Mon, 14 Apr 1997 11:13:43 -0700 [thread overview]
Message-ID: <199704141813.LAA19102@titian.engr.sgi.com> (raw)
Could someone tell me how big the kernel is for the MIPS chip? I
need a rough estimate of the size of a minimal kernel with networking
support, probably no file systems nor disks. A project I'm working on
is currently using VxWorks. We're suppose to add a bunch of large, off
the shelf software components to it and I'm worried about running
everything in one unprotected address space. (All it takes is the web
browser to hickup and the box will crash. But hey, no one has ever
heard of a web browser crashing!) Does anyone have an estimate of the
process switching time? That's one of the things the hardware types
harp about for their multimedia apps.
Thanks
Mike McDonald
mikemac@engr.sgi.com
next reply other threads:[~1997-04-14 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-14 18:13 Mike McDonald [this message]
1997-04-14 18:24 ` How big is the Linux/MIPS kernel? Ariel Faigon
1997-04-14 18:24 ` Ariel Faigon
1997-04-14 18:35 ` Ariel Faigon
1997-04-15 2:13 ` David S. Miller
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=199704141813.LAA19102@titian.engr.sgi.com \
--to=mikemac@titian.engr.sgi.com \
--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