If you have questions about Go you should check out https://github.com/golang/go/wiki/Questions.

No, we don't currently use SO_REUSEPORT on linux.

Can you please explain the problem you are trying to solve that having SO_REUSEPORT available would let you solve?

Go 1.11 probably will fix #9661 instead of exposing a tangle of platform-specific socket options.

@mikioh Noop, I build with master branch 25c3bb3 and it's still missing.

I tried to run src/syscall/mkall.sh on my Debian box to update SO_REUSEPORT but it change const and breaks API checker. Did I miss somethings? :/

-       AF_MAX                           = 0x27
+       AF_MAX                           = 0x2a

@mengzhuo,

The site "godoc.org" is your friend.

https://godoc.org/golang.org/x/sys/unix
https://godoc.org/syscall

If your circumstances have no reachability to the site, unfortunately, https://github.com/golang/go/wiki/Questions could help you.

@mikioh
syscall

This package is locked down. Code outside the standard Go repository should be migrated to use the corresponding package in the golang.org/x/sys repository.

Thanks for your reply, please ignore it :)

@mikioh's previous comment (#23696 (comment)) touches on this obliquely, but more directly:

The syscall.SO_REUSEPORT constant does not exist under linux/amd64, and a few other OS/ARCHes. You have to use golang.org/x/sys/unix.SO_REUSEPORT.