diff options
author | Arnaldo Carvalho de Melo <acme@redhat.com> | 2009-10-12 23:40:10 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2009-10-12 23:40:10 -0700 |
commit | a2e2725541fad72416326798c2d7fa4dafb7d337 (patch) | |
tree | 6174be11da607e83eb8efb3775114ad4d6e0ca3a /usr/Makefile | |
parent | c05e85a06e376f6b6d59e71e5333d707e956d78b (diff) | |
download | linux-a2e2725541fad72416326798c2d7fa4dafb7d337.tar.gz linux-a2e2725541fad72416326798c2d7fa4dafb7d337.tar.bz2 linux-a2e2725541fad72416326798c2d7fa4dafb7d337.zip |
net: Introduce recvmmsg socket syscall
Meaning receive multiple messages, reducing the number of syscalls and
net stack entry/exit operations.
Next patches will introduce mechanisms where protocols that want to
optimize this operation will provide an unlocked_recvmsg operation.
This takes into account comments made by:
. Paul Moore: sock_recvmsg is called only for the first datagram,
sock_recvmsg_nosec is used for the rest.
. Caitlin Bestler: recvmmsg now has a struct timespec timeout, that
works in the same fashion as the ppoll one.
If the underlying protocol returns a datagram with MSG_OOB set, this
will make recvmmsg return right away with as many datagrams (+ the OOB
one) it has received so far.
. RĂ©mi Denis-Courmont & Steven Whitehouse: If we receive N < vlen
datagrams and then recvmsg returns an error, recvmmsg will return
the successfully received datagrams, store the error and return it
in the next call.
This paves the way for a subsequent optimization, sk_prot->unlocked_recvmsg,
where we will be able to acquire the lock only at batch start and end, not at
every underlying recvmsg call.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'usr/Makefile')
0 files changed, 0 insertions, 0 deletions