Difference between revisions of "Afd.sys"
BrentNewland (talk | contribs) m |
|||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | == ReactOS Ancillary Function Driver == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
It was complicated before. Here's how it works now: | It was complicated before. Here's how it works now: | ||
| Line 10: | Line 5: | ||
Each AFD_FCB has a read and write buffer which currently holds up to one packet. For better performance, we can make this buffering scheme better. For the sake of simplicity, it's the way it is now. | Each AFD_FCB has a read and write buffer which currently holds up to one packet. For better performance, we can make this buffering scheme better. For the sake of simplicity, it's the way it is now. | ||
| − | Each socket can have at most one send IRP active at a time. Others either wait or do nothing depending on whether they're for stream or packet sockets. This too can be improved but again does no real harm. | + | Each socket can have at most one send IRP active at a time. Others either wait or do nothing depending on whether they're for stream or packet sockets. This too can be improved but again does no real harm. |
Each socket has at most one receive IRP active at a time (or listen IRP for a listen socket). The TDI provider completes the irp when some data arrives, and we relaunch it when our buffer is empty. | Each socket has at most one receive IRP active at a time (or listen IRP for a listen socket). The TDI provider completes the irp when some data arrives, and we relaunch it when our buffer is empty. | ||
| Line 17: | Line 12: | ||
Apart from that the rest is bookkeeping. | Apart from that the rest is bookkeeping. | ||
| + | |||
| + | {{Code history|drivers/network/afd}} | ||
| + | |||
| + | == External links == | ||
| + | * http://mista.nu/blog/2012/02/17/cve-2012-0148-a-deep-dive-into-afd/ | ||
| + | |||
| + | [[Category:Development]] | ||
| + | [[Category:Drivers]] | ||
Latest revision as of 12:05, 13 June 2014
ReactOS Ancillary Function Driver
It was complicated before. Here's how it works now:
Each AFD_FCB has a read and write buffer which currently holds up to one packet. For better performance, we can make this buffering scheme better. For the sake of simplicity, it's the way it is now.
Each socket can have at most one send IRP active at a time. Others either wait or do nothing depending on whether they're for stream or packet sockets. This too can be improved but again does no real harm.
Each socket has at most one receive IRP active at a time (or listen IRP for a listen socket). The TDI provider completes the irp when some data arrives, and we relaunch it when our buffer is empty.
Select is accomplished by calls to PollReeval in ReceiveComplete, SendComplete, Afd*ReadData and Afd*WriteData. Each time PollReeval is called, a select IRP could get completed.
Apart from that the rest is bookkeeping.
Commit history (Source code can be found in: /reactos/drivers/network/afd)
