From: "Ethan A. Gardener" <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] What are you using Plan 9 for?
Date: Wed, 27 Jun 2018 19:45:31 +0100 [thread overview]
Message-ID: <1530125131.2031840.1422543824.3E1D2B07@webmail.messagingengine.com> (raw)
In-Reply-To: <75E643D1-A04F-4418-AFB0-6E6A7EB21CA1@yingmi.cn>
On Tue, Jun 26, 2018, at 4:24 AM, 刘宇宝 wrote:
>
> Recently I read Rob Pike's "Systems Software Research is Irrelevant", I
> felt pity, and I was wondering what the operating system would look like
> in the future, here is my stupid optimistic predication:
I felt sad when I read it too, but like you, I hope the prevalence of KVM
will bring a new wave of OS development. :)
>
> • Server hardware will become extreme powerful, TB DRAM, non-volatile
> memory, NVMe disk, 100Gb ethernet, the paradigm of separate cpu server,
> file server, (a little fat) terminals will come back to be mainstream,
> network of piles of cheap PCs will go away.
> • Linux,even BSD,became the underlying device driver and "BIOS", this
> is almost the current situation, Linux KVM, Xen + Linux dom0 hide
> details of hardware. This layer takes care maximum hardware support and
> raw performance.
> • *Distributed* operating systems above KVM/Xen will step into a period
> of great development, hardware support and maximum raw performance are
> not top priorities, *OS native* fault tolerance, simple and clear
> distributed process scheduling, easy and consistent IPC/RPC API will
> win, Google Kubernetes will die. Many ideas of Plan 9 will revive, just
> like memory garbage collecting revived after about 30 years.
>
> Regards,
> Yubao Liu
>
next prev parent reply other threads:[~2018-06-27 18:45 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 6:14 刘宇宝
2018-06-12 14:57 ` 刘宇宝
2018-06-14 2:53 ` N. S. Montanaro
2018-06-14 3:53 ` 刘宇宝
2018-06-14 5:17 ` Lucio De Re
2018-06-14 21:12 ` hiro
2018-06-15 0:57 ` 刘宇宝
2018-06-15 2:24 ` N. S. Montanaro
2018-06-15 11:44 ` hiro
2018-06-16 13:39 ` Ole-Hjalmar Kristensen
2018-06-16 15:26 ` Jerome Ibanes
2018-06-21 9:06 ` Rui Carmo
2018-06-21 9:53 ` dexen deVries
[not found] ` <BJXPR01MB0277C36675F3F1EA52FC46EAD44B0@BJXPR01MB0277.CHNPR01.prod.partner.outlook.cn>
2018-06-26 3:24 ` 刘宇宝
2018-06-26 6:36 ` Tyga
2018-06-27 19:10 ` Ethan A. Gardener
2018-06-27 18:45 ` Ethan A. Gardener [this message]
2018-06-14 9:46 ` Tyga
2018-06-14 14:22 ` Steve Simon
2018-06-14 16:15 ` tlaronde
2018-06-14 17:23 ` hiro
2018-06-14 17:45 ` Daniel Camoles
2018-06-15 6:13 ` Mart Zirnask
2018-06-15 13:51 ` Lucio De Re
2018-06-15 14:26 ` hiro
2018-06-15 16:03 ` Mart Zirnask
2018-06-15 17:47 ` Lucio De Re
2018-06-15 19:02 ` Mark van Atten
2018-06-15 23:58 ` Iruatã Souza
2018-06-16 9:35 ` tlaronde
2018-06-18 8:35 ` Mark van Atten
2018-06-14 21:20 ` hiro
2018-06-20 21:35 ` Ethan A. Gardener
2018-06-21 3:58 ` Lucio De Re
2018-06-21 4:49 ` Bakul Shah
2018-06-21 16:02 ` Ethan A. Gardener
2018-06-21 15:23 ` Ethan A. Gardener
2018-06-21 18:03 ` Bakul Shah
2018-06-25 9:33 ` Ethan A. Gardener
2018-06-26 5:17 ` 刘宇宝
2018-06-27 19:01 ` Ethan A. Gardener
2018-06-26 21:03 ` Bakul Shah
2018-06-21 5:39 ` Kurt H Maier
2018-06-21 16:39 ` Ethan A. Gardener
2018-06-21 20:18 ` Skip Tavakkolian
2018-06-28 9:57 ` Richard Miller
2018-06-27 5:18 ` Iruatã Souza
2018-06-28 2:04 ` Tyga
2018-06-21 7:20 ` Mart Zirnask
2018-06-21 15:11 ` Ethan A. Gardener
2018-06-24 8:22 ` 刘宇宝
2018-06-15 8:16 cinap_lenrek
[not found] <1740027127.295380.1529081094082.ref@mail.yahoo.com>
2018-06-15 16:44 ` Brian L. Stuart
2018-06-15 18:16 ` Mark van Atten
[not found] <1401313358.335074.1529087916083.ref@mail.yahoo.com>
2018-06-15 18:38 ` Brian L. Stuart
[not found] <135406475.3232013.1530116414782.ref@mail.yahoo.com>
2018-06-27 16:20 ` Brian L. Stuart
2018-06-28 2:06 ` Tyga
2018-06-28 7:22 ` Mart Zirnask
2018-06-28 18:47 ` Bakul Shah
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=1530125131.2031840.1422543824.3E1D2B07@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).