什么是内核和驱动程序之间的区别？ [英] what is difference between kernel and driver?
问题描述
由于我的主要语言是C ++，并且经常称赞其硬件功能，我决定进入计算机体系结构多一点。由于我一直在寻找通过一些东西，我偶然发现的设备驱动程序。因此，很自然，我决定去看看它。从我的理解，设备驱动程序是用于处理特定硬件组件的计算机程序。我也知道，内核是充当从软件到硬件的桥梁的计算机程序。出于某种原因，我的脑海里无法区分这两个。当涉及到Windows平台上，有人可以解释这种差异对我解释，他们扮演的不同角色。先谢谢了。
Since my primary language is C++, and is often praised for its hardware capabilities, I decided to get into computer architecture a little more. As I was looking through some stuff, I stumbled upon device drivers. So, naturally, I decided to look it up. From my understanding, the device driver is a computer program that handles specific hardware components. I also know that the kernel is a computer program that acts as a bridge from software to hardware. For some reason, my mind can't differentiate the two. When it comes to the windows platform, can somebody explain the difference to me and explain the different roles that they play. Thanks in advance.
推荐答案
如果您缩小内核的类型，即得。单内核，微内核，混合核，外核（更像是应用程序链接到内核库）等，你会看到其中的差别。
If you narrow down the type of kernel, ie. monolithic kernel, micro kernel, hybrid kernel, exokernel (more like application linked into kernel libs), etc, you will see the difference.
例如，在纯单内核，设备驱动程序编译进内核，形成一个单一的实体，而更实际的混合内核，如Windows和Linux，司机是按需为插件来扩展内核特性加载。对于微内核，驱动程序将被视为在其自己的实体应用程序（或服务器）。
For example, in pure monolithic kernel, device drivers are built into the kernel to form a single entity, whereas for more practical hybrid kernel like Windows and Linux, drivers are loaded on demand as "plugin" to extend kernel features. For micro-kernel, drivers are treated as application (or servers) in its own entity.
在一般情况下，驱动器提供详细的实施的具体的物理或逻辑装置，同时内核然后提供一组接口的驱动程序，并在一个较高的抽象级别（HAL）管理它们。
In general, drivers provide detail implementation to specific physical or logical devices, while kernel then provide a set of interface for drivers, and manage them in a higher abstracted level (HAL).
顺便说一句，内核确实比管理硬件资源多了不少。
By the way, kernel does a lot more than managing hardware resources.
这篇关于什么是内核和驱动程序之间的区别？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
