#Keacquirespinlock reactos drivers#
It has some drivers other than the official AFD driver implementation, such as the FASTIO interface is not implemented. Here I refer to the content of AFD in the ReactOS-0.3.4-REL-src source code. AFD does not have official information on its interface, but you can still find a lot of information about AFD drivers on the Internet.
#Keacquirespinlock reactos software#
The AFD driver is actually a TDI client, which uses the TDI interface to call another network component of the micro software TCPIP driver to complete the function. In short, the AFD driver agrees with the SOCKET application interface to implement SOCKET. I drew a legend here to illustrate the relationship between them: It is the realization of the upper SOCKET in the inner core. NDIS and TDI are the programming interface specifications in the kernel network driver model provided by Microsoft, and the AFD driver is a driver component for Microsoft Windows operation. You may know more about NDIS and TDI, while AFD drivers are relatively less.
AFD driveįirst, let's introduce the AFD driver.
The process flow control discussed here is to slow down the process of sending and receiving data according to the user's settings to reduce the bandwidth occupation. Of course, the flow control mentioned here is different from the flow control in the traditional sense. What we are going to discuss is a process flow control scheme based on AFD driver. The effect and complexity of its realization are also different. For example, the application layer is based on LSP, and there are also TDI and NDIS intermediate layers. There are many schemes for controlling process flow, and each scheme has its shortcomings. OverviewĪt present, some software can monitor the process flow, and the functions implemented are many wrong. Key words:AFD process flow control drive 1.
Summary:At present, some software can monitor the process flow, and the functions implemented are many wrong.
0 kommentar(er)
