title: Effect of TCP_CORK
body: <p>I'm having a use case where I'm sending data via TCP/IP in one direction. I'm doing this via multiple <code>send()</code>-calls with very small (in relation to the size of an ethernet frame) payloads (without any flags for the <code>send()</code>-call). To prevent bloating up my small payload packets to the size of a full ethernet frame, I thought it would be nice to use the <code>TCP_CORK</code> socket option. This works, but when actually comparing the situation before and after using <code>TCP_CORK</code>, I noticed that this kind of aggregation was already done. Why is this so? As I said, I do not use any flags for <code>send()</code> (like <code>MSG_MORE</code>) or other socket options, so I would have expected my original solution to be wasteful.</p>