9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] OT: linux complexity trends
Date: Mon, 26 Nov 2001 13:13:04 +0000	[thread overview]
Message-ID: <20011126130655.879E819A2E@mail.cse.psu.edu> (raw)

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

to be fair, i think it depends what that graph is measuring.  if it is
mainly more device drivers and protocols, that increases the scale of
linux, but not necessarily the complexity.  whether some of those
protocols and driver functions really need to be in the kernel might
of course be relevant.  the complexity also isn't a function of size,
but of construction (as a small example i think of all those #ifdefs
in the Linux kernel code i've seen, particularly the powerpc and arm
support).

on the other hand, i think rob observed once years ago at a conference that at
the time the entire source code of the Plan 9 kernel was smaller than
just the include files of some Unix systems, and i don't think that has
changed significantly.


[-- Attachment #2: Type: message/rfc822, Size: 2221 bytes --]

To: 9fans@cse.psu.edu
Subject: [9fans] OT: linux complexity trends
Date: Mon, 26 Nov 2001 12:41:53 +0000
Message-ID: <1171249689@snellwilcox.com>


Linux kernel size trend graph

http://durak.org/sean/pubs/kfc/kfc-size.gif

I wonder what the Plan9 one might look like?

-Steve





----------------------------------------------------------------------
The contents of this communication are confidential to the normal user of
the email address to which it was sent.  If you have received this email
in error, any use, dissemination, forwarding, printing or copying of this
email is strictly prohibited.  If this is the case, please notify the
sender and delete this message.
----------------------------------------------------------------------

             reply	other threads:[~2001-11-26 13:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 13:13 forsyth [this message]
2001-11-26 18:36 ` Dan Cross
2001-11-26 19:45   ` Ronald G Minnich
  -- strict thread matches above, loose matches on Subject: below --
2001-11-26 22:37 forsyth
2001-11-26 19:01 presotto
2001-11-26 17:56 presotto
2001-11-26 18:48 ` Dan Cross
2001-11-27 10:16   ` Thomas Bushnell, BSG
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 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=20011126130655.879E819A2E@mail.cse.psu.edu \
    --to=forsyth@vitanuova.com \
    --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).