From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] OT: critical Intel design flaw
Date: Wed, 3 Jan 2018 09:28:40 -0800 [thread overview]
Message-ID: <C30F8795-EBB0-4734-8550-0BE2B77F07F0@bitblocks.com> (raw)
In-Reply-To: <CAC20D2NEvx_3R_HjzO6r3h6OaAcrpkmWuTRNX7-ApoEz8+KxTg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
On Jan 3, 2018, at 6:26 AM, Clem Cole <clemc at ccc.com> wrote:
>
> Yup microkernels are a tad slower and have more overhead, and might (probably will) cost a little more. But I really do think simplicity beats complexity and I'll pay a bit in over head to keep it simple.
This slowdown (which is not much -- L4 shows it is about 5% or so)
is more due to h/w security architecture that has not evolved for
decades. None of the microkernel research has had any influence on
x86/ARM etc. Look at how Mill solves the problem. A protection
domain switch (a portal call) takes two extra fetches. Second, I
think the protection ring idea was counterproductive. It allowed
people to be lazy and stuff all sorts of things in the kernel.
next prev parent reply other threads:[~2018-01-03 17:28 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 [this message]
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
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=C30F8795-EBB0-4734-8550-0BE2B77F07F0@bitblocks.com \
--to=bakul@bitblocks.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).