NAME
sendmmsg - send multiple messages on a socket
LIBRARY
Standard C library (libc, -lc)
SYNOPSIS
#define _GNU_SOURCE\n /* See feature_test_macros(7) */
\n#include <sys/socket.h>int sendmmsg(int \nsockfd\n, struct mmsghdr *\nmsgvec\n, unsigned int \nvlen\n,\n
\n int \nflags\n);DESCRIPTION
The sendmmsg() system call is an extension of sendmsg(2) that allows the caller to transmit multiple messages on a socket using a single system call. (This has performance benefits for some applications.)
The sockfd argument is the file descriptor of the socket on which data is to be transmitted.
The msgvec argument is a pointer to an array of mmsghdr structures. The size of this array is specified in vlen.
The mmsghdr structure is defined in <sys/socket.h> as:
struct mmsghdr {
\n
struct msghdr msg_hdr; /* Message header */
\n
unsigned int msg_len; /* Number of bytes transmitted */
};The msg_hdr field is a msghdr structure, as described in sendmsg(2). The msg_len field is used to return the number of bytes sent from the message in msg_hdr (i.e., the same as the return value from a single sendmsg(2) call).
The flags argument contains flags ORed together. The flags are the same as for sendmsg(2).
A blocking sendmmsg() call blocks until vlen messages have been sent. A nonblocking call sends as many messages as possible (up to the limit specified by vlen) and returns immediately.
On return from sendmmsg(), the msg_len fields of successive elements of msgvec are updated to contain the number of bytes transmitted from the corresponding msg_hdr. The return value of the call indicates the number of elements of msgvec that have been updated.
RETURN VALUE
On success, sendmmsg() returns the number of messages sent from msgvec; if this is less than vlen, the caller can retry with a further sendmmsg() call to send the remaining messages.
On error, -1 is returned, and errno is set to indicate the error.
ERRORS
Errors are as for sendmsg(2). An error is returned only if no datagrams could be sent. See also BUGS.
STANDARDS
Linux.
HISTORY
Linux 3.0, glibc 2.14.
NOTES
The value specified in vlen is capped to UIO_MAXIOV (1024).
BUGS
If an error occurs after at least one message has been sent, the call succeeds, and returns the number of messages sent. The error code is lost. The caller can retry the transmission, starting at the first failed message, but there is no guarantee that, if an error is returned, it will be the same as the one that was lost on the previous call.
EXAMPLES
The example below uses sendmmsg() to send onetwo and three in two distinct UDP datagrams using one system call. The contents of the first datagram originates from a pair of buffers.
#define _GNU_SOURCE
#include <arpa/inet.h>
#include <netinet/in.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <sys/socket.h>
#include <sys/types.h>
int
main(void)
{
\n
int retval;
\n
int sockfd;
\n
struct iovec msg1[2], msg2;
\n
struct mmsghdr msg[2];
\n
struct sockaddr_in addr;
\n
sockfd = socket(AF_INET, SOCK_DGRAM, 0);
\n
if (sockfd == -1) {
\n
perror("socket()");
\n
exit(EXIT_FAILURE);
\n
}
\n
addr.sin_family = AF_INET;
\n
addr.sin_addr.s_addr = htonl(INADDR_LOOPBACK);
\n
addr.sin_port = htons(1234);
\n
if (connect(sockfd, (struct sockaddr *) &addr, sizeof(addr)) == -1) {
\n
perror("connect()");
\n
exit(EXIT_FAILURE);
\n
}
\n
memset(msg1, 0, sizeof(msg1));
\n
msg1[0].iov_base = "one";
\n
msg1[0].iov_len = 3;
\n
msg1[1].iov_base = "two";
\n
msg1[1].iov_len = 3;
\n
memset(&msg2, 0, sizeof(msg2));
\n
msg2.iov_base = "three";
\n
msg2.iov_len = 5;
\n
memset(msg, 0, sizeof(msg));
\n
msg[0].msg_hdr.msg_iov = msg1;
\n
msg[0].msg_hdr.msg_iovlen = 2;
\n
msg[1].msg_hdr.msg_iov = &msg2;
\n
msg[1].msg_hdr.msg_iovlen = 1;
\n
retval = sendmmsg(sockfd, msg, 2, 0);
\n
if (retval == -1)
\n
perror("sendmmsg()");
\n
else
\n
printf("%d messages sent\n", retval);
\n
exit(0);
}SEE ALSO
recvmmsg(2), sendmsg(2), socket(2), socket(7)