Hi, In-Reply-To: <CAAyB5c+_yBxrer7tA5a69E+-0nsZRCqLV4+MVHEAP_Ppg49whg@xxxxxxxxxxxxxx> On Tue, Jun 30, 2015 at 09:56:50AM -0700, Jerry Jerry wrote: > Hello everyone, > > We currently encounter an issue where we re-use the streams in a SCTP > connection. However, data from different message contexts may co-exist > in the send/recv buffers for that reused stream. I'm wondering if > there is any special API that allow us to flush the data for just one > particular stream in a SCTP connection just before we reuse it, or we > have to do this from application? > > I've been searching but were unable to find a good answer yet. Your > advices would be greatly appreciated! In short, no.. you have to do it in your application. If you're using unordered delivery, I'm afraid that clean cut is just not possible at all as there will always be the chance of a late packet getting delivered. That is, unless you add a layer abstracting that, like a substream id or something like that... And if you're using ordered delivery, it would mean to close/re-open a stream or a signaling for such event, but those operations don't exist. Marcelo -- 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
