sockets - Does listen() backlog affect established TCP connections? -

would naive create tcp socket listen backlog set minimum way of rate limiting new incoming connections? server workload in question doesn't expect many new connections @ time spends lot of time servicing long open persistent connections. appears new incoming connections shouldn't affect established connections, though i've been unable find definitive answer in text. possible failed new incoming connections create kind of tcp traffic congestion on server packets it's receiving or dropped fast enough has no effect on buffers or other part of network stack?

specifically platform in use linux, , although may handled differently in different oss, expect them behave same.

edit mean "same" backlog doesn't affect established connections, though understand linux discards them while windows sends reset.

does listen() backlog affect established tcp connections?

it affects established connections server hasn't accepted yet via accept(), in sense limits number of such connections can exist.

would naive create tcp socket listen backlog set minimum way of rate limiting new incoming connections?

all accomplish unnecessarily fail connecting clients. won't service until server gets around anyway, , once backlog queue fills rate-limited service code anyway. there no particular reason why shortening queue have beneficial effect. other problem idea isn't readily possible determine minimum is, or whether succeeded in setting backlog queue length.

it appears new incoming connections shouldn't affect established connections, though i've been unable find definitive answer in text.

that correct. there no reason why should affect them: that's why won't find written down anywhere, more fact phase of moon doesn't affect either.

is possible failed new incoming connections create kind of tcp traffic congestion on server packets it's receiving

no.

or dropped fast enough has no effect on buffers or other part of network stack?

they're not dropped. aren't created if won't fit on backlog queue. ergo resource consumption @ server zero.

specifically platform in use linux, , although may handled differently in different oss, expect them behave same.

they don't. on windows, incoming connection when backlog queue full causes rst issued. on other platforms ignored.