本文介绍了两种在使用输入/输出完成端口 (IOCP) 时安全释放资源的方法：引用计数(refcounting)和哈希表(hashtable)。通过这两种方式可以有效地管理与套接字相关的会话资源，在适当的时候进行清理。
Usually, these are two ways to safe release resource associated with
IOCP.
The first is using refcounting. When issuing a WSARecv/WSASend,
increase
refcount. When GetQueuedCompletionStatus return, decrease refcount.
It is safe to release resouece when refcount is zero.
The second is using a hashtable. For example, pass SocketHandle to
CreateIoCompletionPort as the completion key, and push the pair --
(SocketHandle, Session) -- into hashtable. When
GetQueuedCompletionStatus
return, get the session from the hashtable by the SocketHandle.
When it need to release the session, remove the pair from the
hashtable first.
After that, when GetQueuedCompletionStatus return, it cannot get the
session
IOCP.
The first is using refcounting. When issuing a WSARecv/WSASend,
increase
refcount. When GetQueuedCompletionStatus return, decrease refcount.
It is safe to release resouece when refcount is zero.
The second is using a hashtable. For example, pass SocketHandle to
CreateIoCompletionPort as the completion key, and push the pair --
(SocketHandle, Session) -- into hashtable. When
GetQueuedCompletionStatus
return, get the session from the hashtable by the SocketHandle.
When it need to release the session, remove the pair from the
hashtable first.
After that, when GetQueuedCompletionStatus return, it cannot get the
session
from the hashtable any more.
http://alt.winsock.programming.narkive.com/68BFIguM/getqueuedcompletionstatus-when-it-s-safe-to-delete-the-completion-key
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
