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

netperf、iperf问题(网络服务) #14

Open
apengaaa opened this issue Feb 27, 2024 · 2 comments
Open

netperf、iperf问题(网络服务) #14

apengaaa opened this issue Feb 27, 2024 · 2 comments

Comments

@apengaaa
Copy link

netperf:

====== netperf UDP_STREAM begin ======
Starting netserver with host '127.0.0.1' port '12865' and family AF_UNSPEC
MIGRATED UDP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 127.0.0.1 (127.0.0) port 0 AF_INET
recv_response_timed_n: no response received. errno 28 counter 0
Hangup
====== netperf UDP_STREAM end: fail ======
====== netperf TCP_STREAM begin ======
MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 127.0.0.1 (127.0.0) port 0 AF_INET
Recv   Send    Send
Socket Socket  Message  Elapsed
Size   Size    Size     Time     Throughput
bytes  bytes   bytes    secs.    10^6bits/sec

 16000  16000   1000    0.05       10.07
accept_connections: select failure: Interrupted system call (errno 4)
====== netperf TCP_STREAM end: success ======
====== netperf UDP_RR begin ======
establish control: are you sure there is a netserver listening on 127.0.0.1 at port 12865?
establish_control could not establish the control connection from 0.0.0.0 port 0 address family AF_UNSPEC to 127.0.0.1 port 12865 address family AF_INET
Unknown signal (core dumped)
====== netperf UDP_RR end: fail ======
====== netperf TCP_RR begin ======
establish control: are you sure there is a netserver listening on 127.0.0.1 at port 12865?
establish_control could not establish the control connection from 0.0.0.0 port 0 address family AF_UNSPEC to 127.0.0.1 port 12865 address family AF_INET
Unknown signal (core dumped)
====== netperf TCP_RR end: fail ======
====== netperf TCP_CRR begin ======
establish control: are you sure there is a netserver listening on 127.0.0.1 at port 12865?
establish_control could not establish the control connection from 0.0.0.0 port 0 address family AF_UNSPEC to 127.0.0.1 port 12865 address family AF_INET
Unknown signal (core dumped)
====== netperf TCP_CRR end: fail ======

iperf:

====== iperf BASIC_UDP begin ======
iperf3: error - unable to receive control message - port may not be available, the other side may have stopped running, etc.: Operation not permitted
Hangup
====== iperf BASIC_UDP end: fail ======

====== iperf BASIC_TCP begin ======
iperf3: error - unable to connect to server - server may have stopped running or use a different port, firewall issue, etc.: Operation not permitted
Hangup
====== iperf BASIC_TCP end: fail ======

====== iperf PARALLEL_UDP begin ======
iperf3: error - unable to connect to server - server may have stopped running or use a different port, firewall issue, etc.: Operation not permitted
Hangup
====== iperf PARALLEL_UDP end: fail ======

====== iperf PARALLEL_TCP begin ======
iperf3: error - unable to connect to server - server may have stopped running or use a different port, firewall issue, etc.: Operation not permitted
Hangup
====== iperf PARALLEL_TCP end: fail ======

====== iperf REVERSE_UDP begin ======
iperf3: error - unable to connect to server - server may have stopped running or use a different port, firewall issue, etc.: Operation not permitted
Hangup
====== iperf REVERSE_UDP end: fail ======

====== iperf REVERSE_TCP begin ======
iperf3: error - unable to connect to server - server may have stopped running or use a different port, firewall issue, etc.: Operation not permitted
Hangup
====== iperf REVERSE_TCP end: fail ======

目前认为是宏内核对网络部分支持不完善

@yfblock
Copy link

yfblock commented Mar 13, 2024

This is the wrong about select syscall instead of network. I remember it was fixed in the x86_64 branch.

@yfblock
Copy link

yfblock commented Mar 13, 2024

This is because the parameter named mask in the pselect syscall will mask some signals in the syscall. But Starry didn't use this parameter. Fixed the issue in the x86_64 branch. There are also some other issues.

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

No branches or pull requests

2 participants