The revenge of the listening sockets

Back in November we wrote a blog post about one latency spike. Today I'd like to share a continuation of that story. As it turns out, the misconfigured rmem setting wasn't the only source of added latency. It looked like Mr. Wolf hadn't finished his job. After adjusting the previously discussed rmem sysctl we continued monitoring our systems' latency. Among other things we measured ping times to o

[moccos_info]

“LHTABLE is small - it has only 32 buckets. LHTABLE is hashed by destination port only.”

[fcicq]

hash collision on LHTABLE https://patchwork.ozlabs.org/patch/79014/