The operating system three structures:
Monolithic ( Monolithic Kernel ) , also known as single-core
Mixed kernel
Microkernel
Presumably we should learn from the fuchsia microkernel architecture:
fuchsia microkernel architecture (pronunciation may be read so? fly by the Sha Haha)
You can look at the article:
https://fuchsia-china.com/huawei-working-fuchsia-sanctions/
Hong Meng operating system advantages:
Use microkernel architecture were achieved operating system
The ability to multi-terminal of sharing each other peripherals
Based on the whole scene distributed microkernel OS
Distributed architecture inherently smooth eco-shared kernel security
Distributed architecture for the first time for cross-terminal terminal OS seamless collaboration experience
High-performance IPC, and reconstruction of the protocol stack of distributed software bus should have a certain relationship?
Distributed Task Scheduling
Distributed Data Management
Hardware virtualization capabilities
Distributed software bus
This distributed architecture to support all Internet wifi network cable network transmission protocol slightly by 2G3G4G5G Bluetooth.
Distributed scheduling software bus hardware capabilities of virtualized resource pools
Distributed software bus protocol , which will streamline the four-layer stack, lifting the payload, the interaction is found connected minimalist faster and faster. Plainly, it is to reconstruct the protocol stack, the reduced header, increases the number of bytes of a single packet transmission. To achieve a minimalist agreement. Improve the transmission efficiency and transmission performance can to a certain extent. But there will be backwards compatibility issues, and the need to re-api interfaces? So it may be based on the application of traditional osi seven layer protocol may not be supported in obscurity operating system, this is just my guess.
Deterministic latency engine , for different processes, using different scheduling priority. Ensure that processes the different needs of timely scheduling, rather than the traditional fair scheduling mode for the server to load the linux. Match application attributes to achieve precise scheduling.
形式化验证方法？ 最新的sosp 2019 上，也出现了使用形式化验证的方法来进行验证文件系统的文章。看来这是一个趋势。论文中如果能对软件系统进行验证。就能使用数学的方法提高说服力。之后可以研究研究。
微内核设计：无root，但一定会有有一个管理员角色的用户存在
这有一定好处，对于用户来说，用户用到root情况很少，使用微内核设计能够提高安全性。但是后期可定制性就会降低。用户不能完全控制自己的设备。有可能自身的计算资源受厂商控制，不能完全调优自己设备的性能。不仅又让我想起了ibm大型机的故事。
鸿蒙操作系统架构：
既然现在内核中包含linux 内核的存在，还有liteOS的存在。也就是说现在 最底层还有一个hypervisor吗？使用虚拟化来进行实现？然后软件使用 分布式软总线进行 传输消息？分布式软总线是用户空间中的一套协议？啥时候能见一见代码呢？
估计之后还是会提供虚拟化层来进行虚拟化api 或者兼容系统调用。因为linux 生态太大了... 等鸿蒙操作系统开源之后再看看吧！
华为ppt上对 程序员的生态 展示也是很友好，不知道真正做起来怎么样？看来又要有一帮华为程序员忙碌在开发和测试的第一线了。这也意味着华为或者国内其他厂商未来需要更多的高素质的系统或者体系结构相关的人才。
按照最近几年华为的新闻，可能鸿蒙操作系统会重点在 x86,x86-64和arm 等体系结构上进行适配调优。
对于鸿蒙系统的兼容性，目前因为存在linux 内核的存在，可能兼容性会好一点，但是如果linux 内核移除之后呢？我对余总的观点表示怀疑。
鸿蒙OS 开源？一定是又用了很多开源代码吧，因为licence所以不得不开源？会不会linux或者fuchsia？不管怎么样，我相信大家都在期待。
视频地址：https://www.bilibili.com/video/av62922095
官方网站：https://developer.huawei.com/consumer/cn/events/hdc2019/index.html
资源来源自网络，欢迎大家一起讨论学习，更多关于系统相关的内容，请关注 cnblogs.com/xuyaowen