> Nick Piggin wrote:
> > But nobody has been able to say why a single kernel is better than a
> > nanokernel.
>
> I think it's a bit more like you haven't realized the answer
> when people
> gave it, so let me try to be more clear. It's purely a
> matter of effort
> - in general it's far easier to write one process than two
> communicating
> processes. As far as APIs, with a single-kernel approach, an RT
> programmer just has to restrict the program to calling APIs
> known to be
> RT-safe (compare with MT-safe programming). In a
> split-kernel approach,
> the programmer has to write RT-kernel support for the APIs he
> wants to
> use (or beg for them to be written). Most programmers would
> much rather
> limit API usage than implement new kernel support themselves.
I strongly support this. It makes a big difference, not only from
the technical point of view (as described above: developers have
to master "two worlds"), but more importantly from the way
management sees things: As soon as some nanokernel or RT plus non-RT
OS approach is mentioned, mgmt fears that there are two different
sources of support (with the usual finger-pointing problems: "Not
our problem, report it to ..."), twice the patches and version
hassles, additional legal issues and runtime license costs/troubles,
two different development environments which must be supported
by the central IT department, ...
When I was told to analyze whether linux is suitable for our
needs, any nanokernel or two-OS approaches were excluded from the
beginning: Mgmt thought that due to their nature and complexity,
such approaches are not able to offer any improvements w.r.t. what
we have now. Clearly, "one system and one source" is wanted!
(we currently use a monolitic, "one-world" OS, but a commercial one)
--
Klaus Kusche (Software Development - Control Systems)
KEBA AG Gewerbepark Urfahr, A-4041 Linz, Austria (Europe)
Tel: +43 / 732 / 7090-3120 Fax: +43 / 732 / 7090-6301
E-Mail: [email protected] WWW: www.keba.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
