Windows异步IO和完成端口(国外英文资料).docVIP

Windows异步IO和完成端口 Windows asynchronous I/O and complete ports Last week, I made a presentation about Windows asynchronous I/O and the completion port technology, focusing on the theory, and the review based on the IOCP network library code. Asynchronous I/O completion port is a, will be the two juxtaposed as the title, because of the complexity of the completion port and USES compared with several other asynchronous I/O combined experience. In Windows core programming, the introduction of asynchronous I/O is clear, and here is a review. First distinguish between two sets of concepts: synchronous/asynchronous (Async/Sync), blocking/non-blocking (blocking/non-blocking) The two sets of concepts are ambiguous, and sometimes they dont have to be clear. I defined these two groups of concepts as a result oriented and a process oriented. Imagine the queues in your life. Impression in the queue is one of the most painful to watch the world expo in Shanghai at the age of 2010, each into a venue to row 2-5 hours, and the weather is hot and dry, queue in the process of abnormal unbearable. Another way to get into a venue is by booking a ticket, which can be put into place on the day of the vote. Hen in line is a kind of synchronous way, until its your turn to go in, in team by hen is asynchronous, two ways are all facing the same results: hen. To wait in the queue process, but only in a team, freedom means the behavior, which is blocked, do anything, and by the can before the hen to any other wanted to go, freedom of action, is also blocked. In this example, you can see why you prefer to be asynchronous and non-blocking, in the program, and the performance difference (see this article). The asynchronous I/O is introduced. The condition of requesting asynchronous I/O Any asynchronous I/O needs to be supported by system facilities, just as the admission ticket is required to have an appointment ticket. Asynchronous I/O request also requires two basic conditions: queue and overlap