All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: Kevin K <k_krieser@sbcglobal.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Driver model.. expel legacy drivers?
Date: Sat, 14 Oct 2006 17:44:00 -0400	[thread overview]
Message-ID: <45315A20.6090600@comcast.net> (raw)
In-Reply-To: <7E4CA247-AD0A-4A20-BEAF-CDD2CA4D3FFE@sbcglobal.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Kevin K wrote:
> 
> On Oct 14, 2006, at 10:04 AM, John Richard Moser wrote:
>> My math predicts that 2.6.57 (+39) will be 100M (in approximately 7
>> years if you assume 1 kernel release every 2 months); 2.6.92 (+35) will
>> breech 200M; 2.6.117 (+25) will breech 300M; and 2.6.138 (+21)) will
>> breech 400M.  That should suffice for predictions over the next 20 years
>> based on this crude model.
>>
> 
> Who knows.  By that time, CPU caches may be that size.  And hopefully
> tools are developed to an extent that they can automate cleanup.
> 

Yeah, a static code coverage analyzer or some sort of code-reducer would
be nice; these are in general pipe dreams but eh.  Also these are
compressed bzip2 tarball sizes, not compiled kernel sizes or source tree
sizes.  I would imagine a 100MB bzip2 would turn into something quite
large; the major issue is the amount of work it takes to maintain
something like that.

I am slowly forming the prediction that monolithic kernels won't survive
(Net/Open/FreeBSD, Linux) and only microkernels or so-called
"nanokernels" (or the exokernel ...) will be maintainable EVENTUALLY;
however I don't have sufficient data, as one would have to illustrate a
maintenance advantage in those models to complete that prediction and I
lack understanding to do such.  Besides, there's no good data on the
upper bound of what is maintainable; it's somewhere below the size of
the universe, that's about all I can give you.



- --
    We will enslave their women, eat their children and rape their
    cattle!
                  -- Bosc, Evil alien overlord from the fifth dimension
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBRTFZkQs1xW0HCTEFAQJs2A//YSjtTW8JR0n+Rz4XrBsib4O1Qgo1CGmd
ybbIQxE1eO8OG/p7uaJuHVaot1CrG6i3+D/hXp5rVAo4hDtnABLCymLtpjGDMM2o
l8tjY2c7qZ2cBwe356xM21eIPXvO0aNy21Etj5mfohtI4OAn0YTdL+tIwDnH/FOH
qLEFB8yXo5ebRRJJByVdnSJzYxzegszwsJk4JchBEuOxHdoA+sX+V/eUCZIUeJ/t
QsKsk5P/ETnPvfEpq2T53wXHba14r+AdbIoxT1q9mKMSZP7KWkn7u5v7J4MGI7JL
/5wWuk9ezjJn9b8ucu4YAJnf1Uojdo06Q6yqIVlB0pg7eGXdJv73lWXet5A4nUoA
VSDHIqJSy7cPkK4JqghbqJO9R0dca8INAhRkkLvj2zEynw6aG2jo90ZGvDzANPzU
QvGbck2uatY88V/Cvyi0XnkdU/cEPjPnx0OC+7yWHVKTF3p/FYuOXSiruBCgmFtX
7ZCMU89ZNhNUED1nMovQQaChqcgbLQdCvaYOhLcNsIkbmt1zUCx1SeTw4+FCxKYZ
qI0YQ/5mv5NQxIdz/kFN8mu0ULxmzTFz4cK3RmELKvxPvbZA+NExV8c99Po9MLSU
obtEbr/s5g11/Vn9DLR5SuA5hSniEcENQkYMAh7JnreYwIGJ/1KS6n6z6jBGcUY6
lkDp86qR3hg=
=Ft1u
-----END PGP SIGNATURE-----

  reply	other threads:[~2006-10-14 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14  3:18 Driver model.. expel legacy drivers? John Richard Moser
2006-10-14  7:56 ` Adrian Bunk
2006-10-14 11:19   ` James Courtier-Dutton
2006-10-14 15:04   ` John Richard Moser
2006-10-14 18:54     ` Horst H. von Brand
2006-10-14 20:48       ` John Richard Moser
2006-10-15 15:31       ` Jan Engelhardt
2006-10-14 21:14     ` Kevin K
2006-10-14 21:44       ` John Richard Moser [this message]
2006-10-15  0:03         ` Alan Cox
2006-10-14 23:51           ` John Richard Moser
2006-10-15  1:24             ` Kevin K
2006-10-15  1:51               ` Alistair John Strachan
2006-10-15 14:33             ` Alan Cox
2006-10-16  9:39               ` Kasper Sandberg
2006-10-16 14:13                 ` Lee Revell
2006-10-16 19:04                   ` Lennart Sorensen

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=45315A20.6090600@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=k_krieser@sbcglobal.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.