From: Helge Hafting <helgehaf@aitel.hist.no>
To: jeff millar <wa1hco@adelphia.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is KERNEL developement finished, yet ???
Date: Fri, 06 Dec 2002 09:55:38 +0100 [thread overview]
Message-ID: <3DF0660A.B26D91D8@aitel.hist.no> (raw)
In-Reply-To: 007301c29cd3$95ad99d0$6a01a8c0@wa1hco
jeff millar wrote:
>
> Harnessing energy (rockets, nukes, etc) is fundamentally an unlimited
> engineering opportunity. But kernel development is mostly an attempt to
> reduce overhead to zero. If a kernel runs 90% efficient now, then there's
> only 10% additional improvement possible.
>
It isn't merely reducing overhead. You can, for example,
develop better caching/readahead/swap algorithms and sometimes
get fantastic improvement.
> On the other hand application software is fundamentally unlimited.
>
> So if you want to work on reliability, portability, maintainability, and
> adaptation to new hardware then kernels make a good career. But if you want
> to break new ground, then it's either application space or hardware.
>
You can break new ground with kernels too - whenever you find
new ways to use the hardware. Kernels for massively parallel
machines aren't standardized yet, for example.
And that's the way hardware may have to go for further improvement
when it hits the final size limits.
Helge Hafting
next prev parent reply other threads:[~2002-12-06 8:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 13:03 cs driver SANTHOSH K
2002-12-04 15:26 ` is KERNEL developement finished, yet ??? Shane Helms
2002-12-04 17:01 ` Joseph D. Wagner
2002-12-04 18:38 ` Alan Cox
2002-12-04 18:07 ` Richard B. Tilley (Brad)
2002-12-04 18:21 ` Richard B. Johnson
2002-12-04 18:39 ` Erik Andersen
2002-12-05 16:59 ` Bill Davidsen
2002-12-05 0:27 ` jeff millar
2002-12-05 23:55 ` Frank van Maarseveen
2002-12-06 0:24 ` Shane Helms
2002-12-06 3:00 ` jeff millar
2002-12-06 3:36 ` Miles Bader
2002-12-06 8:55 ` Helge Hafting [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 2:00 Ed Vance
2002-12-05 12:24 ` Shane Helms
2002-12-05 12:54 ` Joseph D. Wagner
2002-12-05 13:15 ` Andreas Schwab
2002-12-05 18:07 ` Linus Torvalds
2002-12-05 19:52 ` Shane Helms
2002-12-05 20:03 ` Linus Torvalds
2002-12-07 20:34 ` Kai Henningsen
2002-12-05 18:09 ` Alan Cox
2002-12-05 17:47 ` yodaiken
2002-12-05 19:08 ` John Bradford
2002-12-06 6:15 ` Joseph D. Wagner
2002-12-06 6:30 ` John Alvord
2002-12-06 9:48 ` Alvaro Lopes
2002-12-07 20:43 ` Kai Henningsen
2002-12-07 20:39 ` Kai Henningsen
2002-12-09 14:08 ` Jesse Pollard
2002-12-10 0:26 ` H. Peter Anvin
2002-12-05 14:33 ` Mikael Pettersson
2002-12-05 14:58 Nicholas Berry
[not found] <sdef2367.029@mail-02.med.umich.edu>
2002-12-05 15:17 ` Joseph D. Wagner
2002-12-05 15:38 ` Dave Jones
2002-12-05 15:44 ` Eric Weigle
[not found] <sdef301b.011@mail-01.med.umich.edu>
2002-12-05 16:36 ` Joseph D. Wagner
2002-12-06 3:29 ` Keith Adamson
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=3DF0660A.B26D91D8@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=wa1hco@adelphia.net \
/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