Random (stack) walk... Pause for a moment!
So far what we achieved in the WSK investigation?
1) We provide a wsk client and register with wsk provider. This registration process could be at a DriverEntry() routine or it could be in a system thread of a subsystem. The pattern is fairly similar to the user mode WSAStartup() invokation. In the kernel socket scenario, the availability of the provider is important, so need extra caution when we try to capture the NPI interface. Imagine a kernel module that starts pretty early when provider infrastructure ( for example, NETIO, and AFD ) is not available. In such a scenario if we try to capture the provider interface it would not be wise to wait infinitely on the call because that can have an adverse effect on the system boot/load process. You can always craft something to avoid this ( home work :).
2) We have a bit better understanding about the wsk sockets and their types: Basic, Listen, Connection oriented etc.
3) We do have an idea of what subset of allowable dispatches are for what type of wsk sockets.
4) We do have an idea that NETIO is sort of a broker, and AFD is the actual provider of socket functionality.
5) Finally we also looked at some of the data structure pertient to wsk programming.
Prokash Sinha
Post a Comment
1 Reference
References (1)
-
Response: buy papers onlineEvery movement has compulsory for taking the pause as well. Because without pause the human been g will feel tied and lazy as well in front of the people. Which is not only for the perfection of the other?
Reader Comments