On Sun, Apr 15, 2018 at 11:01:47PM +0200, Michael Tuexen wrote: > > On 15. Apr 2018, at 22:41, Pedro Henrique <phamorimrezende@xxxxxxxxx> wrote: > > > > Dear members, > > > > I'm very new to SCTP and don't know if what I'm trying to do is really > > possible without extending the lksctp. Basically, I created a > > connection between two hosts (Client and Server) via the SCTP socket. > > I'm able to successfully send sctp data from the server to the client. > > Moreover, I also created multiple streams on the same connection. Now, > > here is the issue. According to the SCTP documentation, many data > > chunks can be sent inside the same packet. However, for my > > experiments, I would like that only the data chunks belonging to the > > same stream ID are encapsulated in the same packet. Or, in the worst > > case, only one data chunk is encapsulated in each packet. Is any of > > these two approaches possible without changing the lksctp code? If > > not, could someone please help me on how to implement one of these > > approaches in lksctp? > Sounds like you are looking for support of > https://tools.ietf.org/html/rfc8260#section-3.3 > > Not sure it is implemented yet. Not yet. This one in particular is a tricky one for us to implement as the "end of packet" event or so is not directly available where we dequeue chunks for sending. Not impossible, just harder than the others. We have only FCFS, PRIO and RR so far. Cheers, Marcelo > > Best regards > Michael > > > > Thank you, > > Regards, > > > > -- > > Pedro Henrique Amorim Rezende > > -- > > 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 > > -- > 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 > -- 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
