Hello,
The "so" parameter in the TCP zero-copy callback is a "pointer to an internal socket object" according to the documentation. Is it possible to associate this with the socket the data was received on? The "so" parameter does not appear to be associated with the socket handle returned from qapi_accept.
Thanks,
Ryan
qapi_accept
*/qapi_acc
Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.
Yes, we associate the socket handle obtained from the TCP zero-copy callback to qapi_accept.
However, kindly note the qapi_accept will return a new socket descriptor with same propperties od "so" parameter.
Please refer to @target\quartz\demo\QCLI_demo\src\net\Bench_tcp.c for more detailed implementation.