RIOReceive function doesn't work (RIO using IOCP notifications)

범종 김 0

hello.

I want to using RIO for Winsock and IOCP notifications.

naively writes code, source link here .

I regist RIORecevie here

	RIO_NOTIFICATION_COMPLETION type;
...
	type.Type = RIO_IOCP_COMPLETION;
    type.Iocp.IocpHandle = hIOCP;
    type.Iocp.CompletionKey = &g_socket;
    type.Iocp.Overlapped = &overlapped;

...


	RIO_CQ Cqueue = g_rio.RIOCreateCompletionQueue(327680, &type);

...

	RIO_RQ Rqueue = g_rio.RIOCreateRequestQueue(g_socket, 256, 1, 256, 1, Cqueue, Cqueue, NULL);

...

	g_rio.RIOReceive(Rqueue, pBuf, 1, 0, pBuf);

...

	GetQueuedCompletionStatus(hIOCP, &localnumberOfBytes, &localcompletionKey, &localpOverlapped ,INFINITE);

RIOSend function work, so client received data.

but, RIORecevie function doesn't work when client send data.

how to correct my code to work RIORecevie?

Jeanine Zhang-MSFT 9,181 Reputation points Microsoft Vendor

2024-03-18T01:25:09.6033333+00:00

Could you please tell us what do you mean "RIORecevie function doesn't work when client send data."? Whether the RIOReceive function returns TRUE or False? If the function failed, I suggest you could try calling the WSAGetLastError function to get the specific error code.

Refer to the Doc:LPFN_RIORECEIVE callback function
범종 김 0 Reputation points

2024-03-18T10:02:01.81+00:00
thanks for comment, Jeanine Zhang.

RIOReceive function returns 1.

#define TRUE 1

in debug x64 VS community 2022, Windows 10 Pro 22H2.

if the function return TRUE, than the following statements satisfy.

the receive operation is successfully initiated ... from LPFN_RIORECEIVE callback function

but no notification from the socket that registered at RIO Completion Queue.

I think that GetQueuedCompletionStatus function must return when client send data.
Jeanine Zhang-MSFT 9,181 Reputation points Microsoft Vendor

2024-03-20T09:11:22.2166667+00:00

This completion key should be unique for each file handle, and it accompanies the file handle throughout the internal completion queuing process. It is returned in the GetQueuedCompletionStatus function call when a completion packet arrives.

As far as I'm concerned you need to assign unique completion keys for each type of socket.

I suggest you could refer to the links:

https://learn.microsoft.com/en-us/windows/win32/api/ioapiset/nf-ioapiset-createiocompletionport?redirectedfrom=MSDN#remarks https://stackoverflow.com/a/30703519