From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] OT: critical Intel design flaw
Date: Wed, 3 Jan 2018 18:26:04 -0800 [thread overview]
Message-ID: <20180104022604.GL1534@mcvoy.com> (raw)
In-Reply-To: <20180104021414.6EF88156E523@mail.bitblocks.com>
On Wed, Jan 03, 2018 at 06:13:59PM -0800, Bakul Shah wrote:
> > To add to Ted's points. I was good friends with one of the core guys
> > on the QNX team a long time ago (he died early in 1998 of brain cancer.
>
> Dan Hildebrand? I used QNX in 86 and had read his papers but never
> met him.
Yep, great guy. We could argue long and hard but it was always about
the tech, never about the person. An engineer's engineer.
> > The problem is that most people / companies are not that disciplined.
>
> The whole idea is not to hack on the ukernel endlessly but to
> build apps on top of it. On something like Mill you won't even
Um, I've been reading about Mill for at least a decade. It's not
real until it ships. It's still vaporware, no?
> > I'd argue that microkernels are indeed the best answer but only if you
> > have the best programmers. Which nobody does even though everyone claims
> > they do.
> >
> > Monolithic kernels are far more amenable to less than awesome people
> > messing with them. Sad but true, I'd love a microkernel world but I
> > fear we are too stupid to get it. Something, something, something,
> > this is why we can't have nice things.
>
> A monlithic kernel reimplemented as a set of services on top
> of ukernel would be even more amenable.
That's been the claim but there is no data to support that claim. In fact
the opposite. History has shown that microkernels can work if you are
super super careful. Monolithic kernels work in spite of all the idiots
checking in stupid stuff.
I *love* the idea of a microkernel with a bunch of processes implementing
the OS, it's so much a better design. I also have been in the real world
long enough to think that I'm not going to see Linux replaced with a
microkernel in my lifetime. I wish, but I don't see it happening.
--lm
next prev parent reply other threads:[~2018-01-04 2:26 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 13:43 Noel Chiappa
2018-01-03 14:26 ` Clem Cole
2018-01-03 17:28 ` Bakul Shah
2018-01-03 17:46 ` ron minnich
2018-01-03 18:28 ` Bakul Shah
2018-01-03 18:27 ` Clem Cole
2018-01-03 18:39 ` Forrest, Jon
2018-01-03 18:50 ` ron minnich
2018-01-03 19:56 ` Paul Winalski
2018-01-03 20:24 ` Bakul Shah
2018-01-03 23:40 ` Theodore Ts'o
2018-01-04 0:51 ` Larry McVoy
2018-01-04 2:13 ` Bakul Shah
2018-01-04 2:26 ` Larry McVoy [this message]
2018-01-04 3:31 ` Bakul Shah
2018-01-04 2:09 ` Arthur Krewat
2018-01-04 3:21 ` Dan Cross
2018-01-04 17:42 ` Arthur Krewat
2018-01-04 11:53 ` Harald Arnesen
2018-01-04 14:03 ` Clem Cole
2018-01-04 15:54 ` Larry McVoy
2018-01-04 16:45 ` Theodore Ts'o
2018-01-04 17:10 ` Andy Kosela
2018-01-04 17:17 ` Larry McVoy
2018-01-04 18:29 ` Bakul Shah
2018-01-04 18:50 ` Larry McVoy
2018-01-04 20:52 ` Warner Losh
2018-01-04 20:56 ` Bakul Shah
2018-01-04 20:56 ` Theodore Ts'o
2018-01-04 21:16 ` Warner Losh
2018-01-04 22:55 ` Andy Kosela
2018-01-05 14:27 ` Clem Cole
2018-01-04 21:17 ` Bakul Shah
2018-01-04 17:20 ` Tom Ivar Helbekkmo
2018-01-04 17:28 ` Warner Losh
2018-01-03 17:07 ` Bakul Shah
-- strict thread matches above, loose matches on Subject: below --
2018-01-03 17:06 Norman Wilson
2018-01-03 7:53 Andy Kosela
2018-01-03 11:57 ` Ron Natalie
2018-01-03 14:22 ` Random832
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=20180104022604.GL1534@mcvoy.com \
--to=lm@mcvoy.com \
/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).