> > I see. You are looking to remove the limitation of single listening socket. > The SCTP options that Michael pointed out is supposed to behave exactly > as linux SO_REUSEADDR does, i.e it limites to as single listening socket. > > This would have to be added to SCTP protocol. > Yes. Any idea when this can be added to Linux. Also I was curious to know that when UDP supports SO_REUSEPORT, then why SCTP limits it to only one-to-one style and not extend it to one-to-many style socket. Thanx, --Raman On Mon, Sep 22, 2014 at 11:30 PM, Vlad Yasevich <vyasevich@xxxxxxxxx> wrote: > On 09/22/2014 01:39 PM, Raman Gupta wrote: >>> What is missing, in your opinion, from the functionality of SO_REUSEADDR? >>> >> I was looking for multiple SCTP sockets belonging to different server >> instances (process or threads) on the same host to bind to the same >> port. The SO_REUSADDR in SCTP does not currently provide for this >> (errno: Address already in use). The recent introduction of >> SO_REUSEPORT in TCP/UDP for this purpose triggered me for a similar >> solution in SCTP as well, which provides many other benefits also and >> simplifies server scalability design. >> > > I see. You are looking to remove the limitation of single listening socket. > > The SCTP options that Michael pointed out is supposed to behave exactly > as linux SO_REUSEADDR does, i.e it limites to as single listening socket. > > This would have to be added to SCTP protocol. > > -vlad > >> Thanx >> >> --Raman >> >> >> On Mon, Sep 22, 2014 at 10:21 PM, Vlad Yasevich <vyasevich@xxxxxxxxx> wrote: >>> On 09/22/2014 11:59 AM, Raman Gupta wrote: >>>>> Ahh, OK. So it seems Linux doesn't support it... >>>> Any plans to add support for it in Linux. That would make SCTP on par >>>> with TCP/UDP. >>> >>> What is missing, in your opinion, from the functionality of SO_REUSEADDR? >>> >>> -vlad >>> >>>> >>>> Thanx >>>> >>>> --Raman >>>> >>>> >>>> On Mon, Sep 22, 2014 at 7:40 PM, Michael Tuexen >>>> <Michael.Tuexen@xxxxxxxxxxxxxxxxx> wrote: >>>>> On 22 Sep 2014, at 15:07, Raman Gupta <ramangupta16@xxxxxxxxx> wrote: >>>>> >>>>>>>> 1) Even with one-to-one style SCTP socket (SOCK_STREAM) I am getting >>>>>>>> port already in use error. >>>>>>>> 2) SO_REUSEPORT socket option I am setting before calling sctp_bindx. >>>>>>>> 3) The second process which results in port already in use error for >>>>>>>> second, has exactly same code (same binary) as the first process thus >>>>>>>> all SCTP sockets bound to the same port have set the SO_REUSEPORT >>>>>>>> option. >>>>>>>> 4) Using SOL_SOCKET option level >>>>>> >>>>>>> What happens if you use the SCTP level option as described in the link >>>>>>> I provided? >>>>>> >>>>>> I used IPPROTO_SCTP option level in setsockopt() but on running the >>>>>> first process itself I got errno 92 (ENOPROTOOPT 92 /* Protocol not >>>>>> available */ ) when code hits set socket option for SO_REUSEPORT. >>>>> Ahh, OK. So it seems Linux doesn't support it... >>>>> >>>>> Best regards >>>>> Michael >>>>>> >>>>>> Thanx >>>>>> >>>>>> --Raman >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Sep 22, 2014 at 3:18 PM, Michael Tuexen >>>>>> <Michael.Tuexen@xxxxxxxxxxxxxxxxx> wrote: >>>>>>> >>>>>>> On 22 Sep 2014, at 09:57, Raman Gupta <ramangupta16@xxxxxxxxx> wrote: >>>>>>> >>>>>>>>>> The SO_REUSEPORT socket option was introduced in mainstream kernel 3.9 >>>>>>>>>> for TCP/UDP. Is this option supported for SCTP also? >>>>>>>>> Have you looked at >>>>>>>>> https://tools.ietf.org/html/rfc6458#section-8.1.27 >>>>>>>> >>>>>>>> >>>>>>>> 1) Even with one-to-one style SCTP socket (SOCK_STREAM) I am getting >>>>>>>> port already in use error. >>>>>>>> 2) SO_REUSEPORT socket option I am setting before calling sctp_bindx. >>>>>>>> 3) The second process which results in port already in use error for >>>>>>>> second, has exactly same code (same binary) as the first process thus >>>>>>>> all SCTP sockets bound to the same port have set the SO_REUSEPORT >>>>>>>> option. >>>>>>>> 4) Using SOL_SOCKET option level >>>>>>> What happens if you use the SCTP level option as described in the link >>>>>>> I provided? >>>>>>> >>>>>>> Best regards >>>>>>> Michael >>>>>>>> >>>>>>>> I am using centos6 with kernel 2.6.32-431.29.2.el6.x86_64 >>>>>>>> >>>>>>>> Thanx >>>>>>>> >>>>>>>> --Raman >>>>>>>> >>>>>>>> >>>>>>>> On Sun, Sep 21, 2014 at 5:23 PM, Michael Tuexen >>>>>>>> <Michael.Tuexen@xxxxxxxxxxxxxxxxx> wrote: >>>>>>>>> On 21 Sep 2014, at 08:32, Raman Gupta <ramangupta16@xxxxxxxxx> wrote: >>>>>>>>> >>>>>>>>>> The SO_REUSEPORT socket option was introduced in mainstream kernel 3.9 >>>>>>>>>> for TCP/UDP. Is this option supported for SCTP also? >>>>>>>>> Have you looked at >>>>>>>>> https://tools.ietf.org/html/rfc6458#section-8.1.27 >>>>>>>>> >>>>>>>>> Best regards >>>>>>>>> Michael >>>>>>>>>> >>>>>>>>>> The latest centos6 kernel 2.6.32-417.el6 allows this socket option >>>>>>>>>> for SCTP, but does not seem to support it. I get port already in use >>>>>>>>>> error. >>>>>>>>>> -- >>>>>>>>>> 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
