From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kernel modules
Date: Mon, 10 Nov 2003 15:41:30 +0100 [thread overview]
Message-ID: <8d01ecb6b7ce6b634f4ec375651a878f@plan9.escet.urjc.es> (raw)
In-Reply-To: <ef8639e23f04a0595330978dd74d1c0e@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
But then, isn't it reasonable to keep a 9embed
kernel compiled with just a subset of devices for that
sort of platforms?
[-- Attachment #2: Type: message/rfc822, Size: 1892 bytes --]
From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kernel modules
Date: Mon, 10 Nov 2003 09:38:18 -0500
Message-ID: <ef8639e23f04a0595330978dd74d1c0e@plan9.bell-labs.com>
> Is the complexity added worth? For instance,
> my kernel is a 1.9% of the machine memory?? (maybe a 4%
> while running, but that's in a 128M machine, which
> is pretty low these days).
It could be worth while in embedded systems using Plan 9...
next prev parent reply other threads:[~2003-11-10 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 23:50 Fco.J.Ballesteros
2003-11-10 11:46 ` Charles Forsyth
2003-11-10 14:34 ` ron minnich
2003-11-10 14:38 ` Fco.J.Ballesteros
2003-11-10 14:44 ` ron minnich
2003-11-10 14:38 ` Sape Mullender
2003-11-10 14:41 ` Fco.J.Ballesteros [this message]
2003-11-10 14:46 ` ron minnich
2003-11-10 14:48 ` Sape Mullender
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=8d01ecb6b7ce6b634f4ec375651a878f@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.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;
as well as URLs for NNTP newsgroup(s).