-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent behaviors with SO_REUSEPORT on Linux and *BSD #579
Comments
@panjf2000 are these related?
honestly, if i can get luyu6056's tls to work with so reuseport, i'll be contented with the older version use. @panjf2000 should we wait for the tls on gnet? been waiting for this feature for years. but i'm not rushing u. i understand it's insane amount of work. p.s. : i got it "working" with tls here but not with the soreuseport option... need soreuseport. can see if i can use it now on the older version? tlsserver.go (cannot run it twice even with soreuseport option enabled)
tlsclient.go
|
when tlsserver is running...
showing req/s only. very good in fact. just need soreuseport working ...
|
Did it work on Linux? If so, then it's irrelevant. |
@panjf2000 ubuntu 22.04. amd ryzen 5 |
this tls on "old version" is working so fine now in fact (other than so reuseport) that i can really live with it if so reuseport is enabled. i sound so desperate for this feature coz i've stuck with even worst results from this: i really wont be asking for a lot. just tls working with so reuseport... if u know what i mean from testing gnet for so long and needing this tls + so reuseport so badly. |
@panjf2000 also, do u know if you made my version work with so_reuseport, "officially" this is a very good working version of tls for gnet (older version but still gnet) ... and then i will try to figure out how to make it work for https and then http2 coz it's already working with the luyu6056 version, just need to distill down to the actual usage guide |
I'd suggest you look for other alternatives if you're so urgent. |
References
The text was updated successfully, but these errors were encountered: