Home>Article>Operation and Maintenance> What is the difference between linux and vxworks
The difference between linux and vxworks: 1. The kernel structure is different. vxworks is a microkernel and only provides basic services, while linux is a macro kernel. In addition to basic services, the kernel also includes file systems, network protocols, etc.; 2. The running modes are different. The vxworks application is in "real mode" and there is no distinction between user mode and kernel mode, while Linux uses "protected mode". User processes and threads run in user mode, and kernel threads run in kernel mode.
#The operating environment of this tutorial: linux7.3 system, Dell G3 computer.
The operating system I currently use for embedded development is VxWorks. When I was in college, I used the linux operating system most. However, for What are the differences between these two operating systems? I have never really summarized them in detail. When asked by others, it is inevitable to feel a little embarrassed. After all, I am studying embedded development, but I know nothing about embedded development systems. I won’t go into detail, so today I will take some time to summarize it carefully. What is the difference between the two?
## VxWorks | ## linux
||
| Kernel structure ##Microkernel, the kernel only provides the basic |
services, such as: task management, memory management, interrupt handling, etc.Macro kernel, in addition to basic services, internalThe core also includes file systems, network protocols | , etc.##Run mode |
The application runs in "real mode", there is no distinction between user mode and kernel mode |
adopts "protected mode" , user processes and threads run in user mode, kernel threads run in kernel mode |
# #Memory access and memory protection |
| All tasks run in the same physical location , users The program directly operates the physical address, cannot directly provide memory protection, |
cannot prevent error spreadThe kernel adopts Virtual storage management method, the user has an independent address space, the user process can only access the virtual space of this process, providesmemory protection, and can prevent errors Spread | Execution unit ## Task | Processes, threads
Request kernel service method |
Function call, faster | System call, safer |
Real-time performance |
Hard real-time | Soft real-time |
VxWorks is mainly used in telecommunications-level data communications and other products, while Linux is mainly used in consumer, industrial control products, etc. Microkernel, macrokernel kernel A client/server relationship is formed between the components that provide various services and the processes that use such services. This service does not necessarily have to stay in the kernel. It can also be designed and implemented as a "service process", where The only part that must remain in the kernel is inter-process communication. If these services are transferred from the kernel to the process level, then the structure of the kernel itself can be greatly reduced and simplified, and each service process can also be designed and implemented independently. and debugging. Microkernel is a kernel mode that transfers services to processes. It is mainly used in real-time systems and embedded systems, mainly because these systems usually do not have disks, and the entire system must be placed on EPROM is often limited by storage space, and the required services are relatively simple, such as PSOS, VxWorks, etc. The macro kernel is a traditional kernel structure that puts process management, memory management and other service functions into the kernel. It is usually used in general-purpose kernels, such as UNIX, linux, etc. Comparison and analysis of the device driver part Due to the structural separation of the Linux operating system and the Linux boot loader, the device driver between them cannot Universal, of course, we can learn from each other on some hardware-related codes for the chip's hardware initialization. The BOOTROM of VxWorks is the same as the device driver of the running version, because the structure of its running version and BOOTROM are consistent and use the same operating system kernel. The device driver of the Linux operating system runs in the kernel space, and the user process runs in the user space. In the Linux operating system, the memory management and mapping methods of kernel space and user space are different. Applications and device drivers will involve different memory spaces during data exchange, which will affect certain efficiency. However, this problem can be solved by modifying the system. Memory space configuration and other methods to solve. The VxWorks operating system does not separate kernel space and user space. Device drivers and applications all run in the same space, and each other's memory can be accessed. Data exchange is very convenient, but the stability of this structure is not as good as that of the Linux system. Both Operating systems provide many device driver resources and templates. However, due to the open source nature of Linux, the type and number of device drivers it provides far exceeds that of VxWorks. Recommended learning:Linux video tutorial |
The above is the detailed content of What is the difference between linux and vxworks. For more information, please follow other related articles on the PHP Chinese website!