This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author malversan
Recipients asvetlov, callumquick, malversan, yselivanov
Date 2019-11-04.19:42:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572896567.61.0.584102817578.issue38285@roundup.psfhosted.org>
In-reply-to
Content
In my scenario that buffer overrun never happens, maybe because I use messages that are not big enough to overflow the default recv() buffer size.

But I think I can confirm that multiple messages are never received in an atomic read, even if they are being issued intensively in short millisecond intervals. Even more, I think there is a recvmmsg() call specific for that purpose if you want to receive multiple reads at once.

As I said I do not have the answers, I rely on the high-level definitions and have little knowledge about how it works at low level.

But I think your question may be extended also to recvmsg(). What is its behaviour if it fills all the passed iovec structs?

Probably an answer can be found where you found the recommendation of using recvmsg() over recv(). There should be a reason for that recommendation.
History
Date User Action Args
2019-11-04 19:42:47malversansetrecipients: + malversan, asvetlov, yselivanov, callumquick
2019-11-04 19:42:47malversansetmessageid: <1572896567.61.0.584102817578.issue38285@roundup.psfhosted.org>
2019-11-04 19:42:47malversanlinkissue38285 messages
2019-11-04 19:42:47malversancreate