The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Gilmore <gnu@toad.com>
To: Andrew Warkentin <andreww591@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] QNX
Date: Mon, 08 Feb 2021 23:42:34 -0800	[thread overview]
Message-ID: <8092.1612856554@hop.toad.com> (raw)
In-Reply-To: <CAD-qYGrbFhrjtWgAxRxMBCtV812zM38zAphyaE-+1ehhT3795g@mail.gmail.com>

Andrew Warkentin <andreww591@gmail.com> wrote:
> A lot of people still seem to believe that microkernels are inherently
> slow, even though fast microkernels (specifically QNX) predate the
> slow ones by several years.

Wait, are we talking about the same operating system called QNX?

We had a customer at Cygnus in the 1990s (perhaps QNX itself) who wanted
us to port the GNU compilers to it.  It was the slowest, buggiest system
we ever tried to run our code on.  I think they claimed POSIX
compatibility; hollow laugh!  It was more like 1970's compatibility.  It
had 14-character file names, the shell and utilities regularly
core-dumped when doing ordinary work, everything had built-in random
undocumented line length limits and file size limits and such (which was
also true in V7 -- that's one thing Richard Stallman insisted on fixing
in every GNU utility; see the GNU Coding Standards).

Our GNU compiler tools ran everywhere, they hosted and bootstrapped on
everything.  Everything except QNX.  Shell scripts and makefiles that
worked on a hundred other UNIX systems were impossible to get working on
QNX.  I think we reported dozens of QNX bugs to the vendor, most of which
never got fixed.

Perhaps somewhere under all that crud there was some kind of "fast
microkernel", but you couldn't prove it by me.  By the time it got to
user code, the only thing it was fast at was failing.  We were trying to
do real work on it, and gave up after some engineers turned the air blue
with incredulous exclamations.  I think we ended up cross-compiling the
GNU compilers for it, from some sane system.  They still had to fix a
bunch of bugs in their libraries that we had to link with.

I realize this flame is not about microkernels.  But perhaps if they had
spent less time optimizing cache hits in the microkernel, the rest of
their system wouldn't have been shot full of obvious holes.

	John

  reply	other threads:[~2021-02-09  7:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 18:11 [TUHS] Macs and future unix derivatives Will Senn
2021-02-08 18:21 ` Larry McVoy
2021-02-08 18:32   ` Justin Coffey
2021-02-08 18:39     ` Larry McVoy
2021-02-09  1:59     ` Theodore Ts'o
2021-02-12 13:48     ` Angel M Alganza
2021-02-08 18:42 ` Henry Bent
2021-02-09  6:55   ` John Gilmore
2021-02-09  7:05     ` Michael Huff
2021-02-16 22:55       ` Greg A. Woods
2021-02-09  7:17     ` Will Senn
2021-02-09 19:02     ` Theodore Ts'o
2021-02-10  1:34       ` Larry McVoy
2021-02-09 22:59     ` Wesley Parish
2021-02-08 18:43 ` Dan Stromberg
2021-02-12 13:39   ` Angel M Alganza
2021-02-08 18:45 ` Thomas Paulsen
2021-02-25 22:45   ` Dave Horsfall
2021-02-08 20:07 ` Al Kossow
2021-02-09  5:10 ` Andrew Warkentin
2021-02-09  7:42   ` John Gilmore [this message]
2021-02-09 11:03     ` [TUHS] QNX Robert Brockway
2021-02-09 18:24       ` Nemo Nusquam
2021-02-09 20:18         ` Jose R Valverde via TUHS
2021-02-09 14:05     ` Larry McVoy

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=8092.1612856554@hop.toad.com \
    --to=gnu@toad.com \
    --cc=andreww591@gmail.com \
    --cc=tuhs@minnie.tuhs.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;
as well as URLs for NNTP newsgroup(s).