9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] kernel modules
Date: Sat,  8 Nov 2003 00:50:11 +0100	[thread overview]
Message-ID: <2b7b451e1182a260aa2887e810b907f4@plan9.escet.urjc.es> (raw)

Maybe I'm wrong, because I'm kind of sleepy, but I think
that you said that the plan was to add loadable module
support and after that, maybe put usb (and perhaps others)
into the kernel.

I've been thinking about it and I think it's not a problem
at all to have everything compiled inside the kernel.
I know this does not include all allocated memory in use
by the kernel, but

872411t + 1555144d + 108904b = 2536459	9pcdisk

2.5 Mbytes (say, 5 Mbytes while running)
is a pretty low ammount of memory this days. Of course this
does not account for fossil et al.

Isn't it enought just to be able to power on/off the
different devices? Even when they contend for a resource,
we can shut down all but the one that we want. There's no
need to load/unload them.

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).

I'd love to see this thing stay as simple as feasible;
just had to say it.



             reply	other threads:[~2003-11-07 23:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-07 23:50 Fco.J.Ballesteros [this message]
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
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=2b7b451e1182a260aa2887e810b907f4@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).