From: "Thomas Bushnell, BSG" <tb+usenet@becket.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] OT: linux complexity trends
Date: Tue, 27 Nov 2001 10:16:31 +0000 [thread overview]
Message-ID: <877kscww8d.fsf@becket.becket.net> (raw)
In-Reply-To: <200111261848.NAA11804@augusta.math.psu.edu>
cross@math.psu.edu (Dan Cross) writes:
> I guess I'm having a hard time understanding the point. Memory being
> as cheap as it is [*], why not just keep the drivers loaded all the time?
> Is this to avoid inter-driver conflicts or to better support PCMCIA
> devices or something?
The usual reason for dynamically loadable device drivers is for:
Systems with easily pluggable hardware (USB, PCMCIA)
Systems where it's beneficial to run one kernel for a bunch of
machines with divergent hardware.
Such systems need all the drivers available, in principle, all the
time, but only a minority will be needed at any one point in time. If
all the supported hardware drivers are loaded at once, you do get
considerable bloat. There are a *lot* of hardware devices out there;
a kernel with device drivers compiled in for all of them would be
insanely huge.
next prev parent reply other threads:[~2001-11-27 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 17:56 presotto
2001-11-26 18:48 ` Dan Cross
2001-11-27 10:16 ` Thomas Bushnell, BSG [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-26 22:37 forsyth
2001-11-26 19:01 presotto
2001-11-26 14:54 rob pike
2001-11-26 17:40 ` Ronald G Minnich
2001-11-26 18:24 ` Alexander Viro
2001-11-26 14:42 forsyth
2001-11-26 14:00 presotto
2001-11-26 13:13 forsyth
2001-11-26 18:36 ` Dan Cross
2001-11-26 19:45 ` Ronald G Minnich
2001-11-26 12:41 steve.simon
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=877kscww8d.fsf@becket.becket.net \
--to=tb+usenet@becket.net \
--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).