public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tommy Reynolds <Tommy.Reynolds@MegaCoder.com>
To: linux-kernel@vger.kernel.org
Subject: Re: monoholitic, hybrid or not monoholitic?
Date: Wed, 15 Sep 2004 19:22:31 -0500	[thread overview]
Message-ID: <20040915192231.1153a0d4.Tommy.Reynolds@MegaCoder.com> (raw)
In-Reply-To: <20040915141237.GB2429@teh.ath.cx>

[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]

Uttered Matt Kavanagh <matthew@teh.ath.cx>, spake thus:

> > the kernel were mostly descripted as monoholitic. but some sources means
> > that the linux kernel is not really monoholitic because of the feature
> > of loading kernel modules.
> I'd tend towards monolithic because the modules (as mentioned) run in kernel
> space.

These discussions are taking the wrong viewpoint.  The difference
between "monolithic" and "modular" kernels refers to their *internal*
organization, not a cosmetic *packaging* decision.

Linux is a monolithic kernel because one kernel routine can call
another directly, without intervention of any message passing
overhead.

Linux modules are simply packaging exercises that allow some code
_not_ originally linked into the kernel image to be grafted into an
executing kernel image.  Once installed, kernel modules can reference
other kernel resources with, again, a straight subroutine reference
without any message passing intervention.

All else is quibbling about the color of the ribbon used to wrap up
the module code ;-)

HTH.
-- 
-- 
.---------------------------------+----------------------------------------.
| Tommy Reynolds                  | Email: <Tommy.Reynolds@MegaCoder.com>  |
| P O Box 62                      | Phone: +1.256.227.1839                 |
| Danville, AL 35619 USA          | Fax:   +1.256.350.5099                 |
| Sr. Software Devel/RHCE         | IM:    HisDivShadow                    |
+---------------------------------+----------------------------------------+
|                     Ask MegaCoder.com For Answers!                       |
'--------------------------------------------------------------------------'
-- 
-- 
.---------------------------------+----------------------------------------.
| Tommy Reynolds                  | Email: <Tommy.Reynolds@MegaCoder.com>  |
| P O Box 62                      | Phone: +1.256.227.1839                 |
| Danville, AL 35619 USA          | Fax:   +1.256.350.5099                 |
| Sr. Software Devel/RHCE         | IM:    HisDivShadow                    |
+---------------------------------+----------------------------------------+
|                     Ask MegaCoder.com For Answers!                       |
'--------------------------------------------------------------------------'

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-09-16  0:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-15 11:27 monoholitic, hybrid or not monoholitic? Patrick Kiwitter- Mailinglist
2004-09-15 12:59 ` Luca Ferroni
2004-09-15 14:12 ` Matt Kavanagh
2004-09-16  0:22   ` Tommy Reynolds [this message]
2004-09-16  1:18     ` Kurt Wall
2004-09-16  0:51   ` monoholitic, hybrid or not monoholitic? [OT] Neil Brown
2004-09-16  9:57     ` Matt Kavanagh

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=20040915192231.1153a0d4.Tommy.Reynolds@MegaCoder.com \
    --to=tommy.reynolds@megacoder.com \
    --cc=linux-kernel@vger.kernel.org \
    /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