Discussion
Loading...
Post
@saper yep, but inconclusive and similarly looking, the biggest being syscall.Syscall6. Nothing obvs wrt fast vs slow
@miek what is Syscall6 ? lstat(2)?
@saper godoc syscall.Syscall6
package syscall // import "syscall"
func Syscall6(trap, a1, a2, a3, a4, a5, a6 uintptr) (r1, r2 uintptr, err Errno)
this must be the read and writes of the socket
@miek could be sendto(2) and/or recvfrom(2) as both take 5 args (plus syscall number). Would be great to check. Are they all non-blocking?
@saper how?
for reading I use https://pkg.go.dev/golang.org/x/net/ipv6#PacketConn.ReadBatch
which should be using recmmsg underneath
@miek can’t follow go source code easily at the moment… if a blocking call is what you want, so here it is, waiting for a packet…. otherwise you might want not to block and read some other sockets maybe while you wait (don’t know your code).
If the speed of network interfaces+drivers is comparable on amd64 and arm64 that would explain why you get similar packet rates. One only need to verify this
1 more replies (not shown)
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled