You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering about the values shown in the toString() method of ChannelInformation, for
parameters "system send buffer size" and "system receive buffer size".
I made a test and set parameter "<SysSendBufSize>" in the "<Channel>" section for my test provider.
I noticed, that the value is passed as number of bytes to the call setsockopt(.. SO_SNDBUF ..).
(On a Linux system you observe different values afterwards in the ChannelInformation,
because setsockopt(.. SO_SNDBUF ..) internally doubles the value and also clips it to a limited range, see man page.).
However, the configured value is obviously applied as number of bytes, and not kilo bytes, as stated in the configuration guide:
"Specifies the size (in KB) of the system's send buffer for this channel."
So there is a contradiction, Regards, Michael Zuck
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Hello.
I was wondering about the values shown in the toString() method of ChannelInformation, for
parameters "system send buffer size" and "system receive buffer size".
I made a test and set parameter "<SysSendBufSize>" in the "<Channel>" section for my test provider.
I noticed, that the value is passed as number of bytes to the call setsockopt(.. SO_SNDBUF ..).
(On a Linux system you observe different values afterwards in the ChannelInformation,
because setsockopt(.. SO_SNDBUF ..) internally doubles the value and also clips it to a limited range, see man page.).
However, the configured value is obviously applied as number of bytes, and not kilo bytes, as stated in the configuration guide:
"Specifies the size (in KB) of the system's send buffer for this channel."
So there is a contradiction, Regards, Michael Zuck
The text was updated successfully, but these errors were encountered: