Home
last modified time | relevance | path

Searched refs:MSG_ZEROCOPY (Results 1 – 7 of 7) sorted by relevance

/Linux-v4.19/tools/testing/selftests/net/
Dudpgso_bench_tx.c37 #ifndef MSG_ZEROCOPY
38 #define MSG_ZEROCOPY 0x4000000 macro
134 cfg_zerocopy ? MSG_ZEROCOPY : 0); in send_tcp()
154 ret = sendto(fd, data, len, cfg_zerocopy ? MSG_ZEROCOPY : 0, in send_udp()
195 ret = sendmmsg(fd, mmsgs, i, cfg_zerocopy ? MSG_ZEROCOPY : 0); in send_udp_sendmmsg()
233 ret = sendmsg(fd, &msg, cfg_zerocopy ? MSG_ZEROCOPY : 0); in send_udp_segment()
Dtcp_mmap.c84 #ifndef MSG_ZEROCOPY
85 #define MSG_ZEROCOPY 0x4000000 macro
439 wr = send(fd, buffer, wr, zflg ? MSG_ZEROCOPY : 0); in main()
Dmsg_zerocopy.c73 #ifndef MSG_ZEROCOPY
74 #define MSG_ZEROCOPY 0x4000000 macro
196 flags |= MSG_ZEROCOPY; in do_sendmsg()
/Linux-v4.19/Documentation/networking/
Dmsg_zerocopy.rst3 MSG_ZEROCOPY chapter
9 The MSG_ZEROCOPY flag enables copy avoidance for socket send calls.
18 such as sendpage and splice. The MSG_ZEROCOPY flag extends the
23 notification overhead. As a result, MSG_ZEROCOPY is generally only
34 Converting an existing application to MSG_ZEROCOPY is not always as
52 [PATCH net-next v4 0/9] socket sendmsg MSG_ZEROCOPY
59 Passing the MSG_ZEROCOPY flag is the most obvious step to enable copy
83 ret = send(fd, buf, sizeof(buf), MSG_ZEROCOPY);
108 MSG_ZEROCOPY that successfully sends data increments the counter. The
208 Passing flag MSG_ZEROCOPY is a hint to the kernel to apply copy
[all …]
/Linux-v4.19/include/linux/
Dsocket.h294 #define MSG_ZEROCOPY 0x4000000 /* Use user data in kernel path */ macro
/Linux-v4.19/net/rds/
Dsend.c928 if ((msg->msg_flags & MSG_ZEROCOPY) && !zcopy_cookie) in rds_rm_size()
1083 bool zcopy = ((msg->msg_flags & MSG_ZEROCOPY) && in rds_sendmsg()
1090 if (msg->msg_flags & ~(MSG_DONTWAIT | MSG_CMSG_COMPAT | MSG_ZEROCOPY)) { in rds_sendmsg()
/Linux-v4.19/net/ipv4/
Dtcp.c1188 if (flags & MSG_ZEROCOPY && size && sock_flag(sk, SOCK_ZEROCOPY)) { in tcp_sendmsg_locked()