how do socket works internally between sendto()/recvfrom()?
I am trying to reduce packets manipulation to its minimum in order to improve efficiency of a specific program i am working on but i am struggling with the time it takes to send through a udp socket using sendto/recvfrom. I am using 2 very basic processes (applications), one is sending, the other one receiving.
I am willing to understand how linux internally works when using these function calls...
Here are my observations: when sending packets at:
•10Kbps, the time it takes for the messages to go from one application to the other is about 28us
•400Kbps, the time it takes for the messages to go from one application to the other is about 25us
•4Mbps, the time it takes for the messages to go from one application to the other is about 20us
•40Mbps, the time it takes for the messages to go from one application to the other is about 18us
When using different CPUs, time is obviously different but consistent with those observations. There must be some sort of setting that enables some queue readings to be done faster depending on the traffic flow on a socket... how can that be controlled?
When using a node as a forwarding node only, going in and out takes about 8us when using 400Kbps flow, i want to converge to this value as much as i can. 25us is not acceptable and deemed to slow (it is obvious that this is way less than the delay between each packet anyway... but the point is to be able to eventually have a greater deal of packets to be processed, hence, this time needs to be shortened!). Is there anything faster than sendto/recvfrom (must use 2 different applications (processes), i know i cannot use a monolitic block, thus i need info to be sent on a socket)?
thanks a lot to all of you guys
|
