Skip to content
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

net: enable native golang linux networking #4498

Open
wants to merge 12 commits into
base: dev
Choose a base branch
from

Conversation

leongross
Copy link
Contributor

@leongross leongross commented Oct 4, 2024

This is a rework of the plain linux network POC #4460. This PR adds adaptive switching of network packages depending on the GOOS.

The CI fails due to unadjusted build tags for MacOs and WASm.
Successfully tested on linux/amd64.

@leongross leongross force-pushed the net-linux-nonlinux branch 7 times, most recently from bbd514e to fdc75d6 Compare October 8, 2024 09:35
@leongross leongross marked this pull request as ready for review October 8, 2024 09:47
Copy link
Member

@aykevl aykevl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How did you test this?

To accept this into TinyGo, I'd like to see at least some tests. For example, you can create a new test like testdata/net.go (and add it to main_test.go for Linux only). It doesn't have to be exhaustive, but for example you can start a socket server (net.Listen) in a goroutine and try to connect to it from the same program.

loader/goroot.go Outdated Show resolved Hide resolved
.gitmodules Show resolved Hide resolved
Comment on lines 7 to 9
panic("todo: semacquire")
// TODO the "net" pkg calls this, so panic() isn't an option. Right
// now, just ignore the call.
// panic("todo: semacquire")
Copy link
Member

@aykevl aykevl Oct 10, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't do this. There is a very good reason this panics: it is a reminder this should be implemented when it is used.
So either restore the panic, or actually implement semacquire and semrelease.

(It's probably easier to implement the internal/poll package instead in a way that works with TinyGo - but even that might be rather complex).

Copy link
Contributor Author

@leongross leongross Oct 28, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe I am missing something here, but since tinygo at the moment only supports a single os thread, it would be sufficient to implement this using a simple mutex, right? Making this code panic will eventually reduce usability for this drastically.

Copy link
Member

@aykevl aykevl Nov 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. All this API provides is a uint32 to store state. That's not enough to store a queue of waiting goroutines and the counter as would be needed for proper semaphore support. I don't think this can even be implemented in the current scheduler - at leat, not without some expensive data structures on the side. It is relatively easy to implement with a futex though, as I have in my threading PR: #4559

src/os/exec.go Show resolved Hide resolved
@leongross
Copy link
Contributor Author

@aykevl I will add some basic tests. Since I already did some testing (I hope) it should be fairly easy to integrate this here.

Signed-off-by: leongross <[email protected]>
if this does not work, do the folliwing steps:
1. remove net submodule
2. remove symlink in local ~/.cache/tinygo/goroot-<hash>/net
3. manual symlink yo local golang /usr/local/bin/src/net

Signed-off-by: leongross <[email protected]>
Signed-off-by: leongross <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants