From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kernel modules
Date: Mon, 10 Nov 2003 07:34:30 -0700 [thread overview]
Message-ID: <Pine.LNX.4.44.0311100731200.5100-100000@maxroach.lanl.gov> (raw)
In-Reply-To: <2b7b451e1182a260aa2887e810b907f4@plan9.escet.urjc.es>
On Sat, 8 Nov 2003, Fco.J.Ballesteros wrote:
> 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).
my modules tree for my laptop, which is hardly complete, is 14MB. Other
machines have 24 MB.
The idea still might work, though. If modules can be avoided that is all
to the good ...
ron
next prev parent reply other threads:[~2003-11-10 14:34 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 [this message]
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
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=Pine.LNX.4.44.0311100731200.5100-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--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).