You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we read a file with this test app (calling read or __read_chk), I observed that we do not produce an fs.read metric event. Also, in the fs.close event associated with the file read, file_read_bytes does not change from 0.
- In the case of the `host` application [1], the `host` app uses
`libuv` to perform the DNS lookup.
- `uv__udp_sendmsg` uses the `syscall` to perform the sending message operation.
The decision of whether to use `syscall` or `sendmsg` is based on checking the value of the
`uv__sendmmsg_avail` variable in `uv__udp_sendmsg` [2].
- `uv__udp_recvmsg` uses `recvmsg` to perform the receiving message operation.
The decision of whether to use `syscall` or `recvmsg` is based on checking the result
of `uv_udp_using_recvmmsg` [3].
- The above explains why `libuv` uses `syscall` for sending messages and `recvmsg` for receiving messages.
- Additionally `libuv` check support for `recvmmsg()` and `sendmmsg()` using
`uv__udp_mmsg_init` with calling `uv__sendmmsg(s, NULL, 0, 0)` [4]
The stack traces for the and `uv__udp_sendmsg` and `uv__udp_recvmsg`:
```
[#0] syscall()
[#1] uv__sendmmsg(...)
[#2] uv__udp_sendmmsg(..)
[#3] uv__udp_sendmsg(...)
[#4] uv__udp_send(...)
[#5] uv_udp_send(...)
```
```
[#0] recvmsg
[#1] uv__udp_recvmsg
```
Ref:
[1] https://github.com/isc-projects/bind9
[2] libuv/libuv@3d71366
[3] libuv/libuv@6b5aa66
[4] libuv/libuv@3d71366
Closes: #1586
When we read a file with this test app (calling
read
or__read_chk
), I observed that we do not produce an fs.read metric event. Also, in the fs.close event associated with the file read,file_read_bytes
does not change from 0.We do see expected results using other commands:
The text was updated successfully, but these errors were encountered: