From: Xin Long > Sent: 18 February 2017 17:53 > This patch is to add support for MSG_MORE on sctp. > > It adds force_delay in sctp_datamsg to save MSG_MORE, and sets it after > creating datamsg according to the send flag. sctp_packet_can_append_data > then uses it to decide if the chunks of this msg will be sent at once or > delay it. > > Note that unlike [1], this patch saves MSG_MORE in datamsg, instead of > in assoc. As sctp enqueues the chunks first, then dequeue them one by > one. If it's saved in assoc,the current msg's send flag (MSG_MORE) may > affect other chunks' bundling. I thought about that and decided that the MSG_MORE flag on the last data chunk was the only one that mattered. Indeed looking at any others is broken. Consider what happens if you have two small chunks queued, the first with MSG_MORE set, the second with it clear. I think that sctp_outq_flush() will look at the first chunk and decide it doesn't need to do anything because sctp_packet_transmit_chunk() returns SCTP_XMIT_DELAY. The data chunk with MSG_MORE clear won't even be looked at. So the data will never be sent. I wouldn't worry about having messages queued that have MSG_MORE clean when the final message has it set. While it might be 'nice' to send the data (would have to be tx credit) waiting for the next data chunk shouldn't be a problem. I'm not sure I even want to test the current patch! David -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
