On Thu, 4 Jun 1998, Rob Walker wrote:
> Eric> Maybe someone who plays with development kernels can answer
> Eric> this: When configuring a new kernel, why would you want to
> Eric> answer 'yes' when a 'module' selection is available?  And for
> 
> speed.  going through a module is slower than not.

Err, once the module is loaded, the speed is identical. However, a module
does use marginally more memory (a module's code segment takes up pages
corresponding to VM pages, while a compiled-in driver takes up exactly how
much space it needs). Thus an average module will waste PAGE_SIZE/2 bytes
(where PAGE_SIZE depends on what MMU you're using and how the Linux port
to that particular architecture uses that MMU). 

The idea of compiling in those drivers that you know you'll need can save
a few K. For those of us with 64MB of RAM, that's not a good enough reason
to give up the flexibility of modules. For folks using an 8M machine as a
router, that's a different story. 

Eric Lee Green   [EMAIL PROTECTED]          Executive Consultants
Systems Specialist               Educational Administration Solutions
             See http://members.tripod.com/~e_l_green


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to