diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2017-04-20 16:42:14 +0200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2017-04-20 16:44:50 +0200 |
| commit | bb67614554b8300cb52251d6daadb851907eb440 (patch) | |
| tree | f1b4ff2afac26db77163865a4f03381bd9573247 /man7/socket.7 | |
| parent | a99fa5fb93420d2c9f0f54c6543dd39941b1c73d (diff) | |
| download | man-pages-bb67614554b8300cb52251d6daadb851907eb440.tar.gz | |
socket.7: srcfix
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man7/socket.7')
| -rw-r--r-- | man7/socket.7 | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/man7/socket.7 b/man7/socket.7 index 81e15b663b..398d5cf561 100644 --- a/man7/socket.7 +++ b/man7/socket.7 @@ -511,6 +511,24 @@ the typical use case is to employ one listening process per RX queue, with the incoming flow being handled by a listener on the same CPU that is handling the RX queue. This provides optimal NUMA behavior and keeps CPU caches hot. +.\" +.\" From an email conversation with Eric Dumazet: +.\" >> Note that setting the option is not supported if SO_REUSEPORT is used. +.\" > +.\" > Please define "not supported". Does this yield an API diagnostic? +.\" > If so, what is it? +.\" > +.\" >> Socket will be selected from an array, either by a hash or BPF program +.\" >> that has no access to this information. +.\" > +.\" > Sorry -- I'm lost here. How does this comment relate to the proposed +.\" > man page text above? +.\" +.\" Simply that : +.\" +.\" If an application uses both SO_INCOMING_CPU and SO_REUSEPORT, then +.\" SO_REUSEPORT logic, selecting the socket to receive the packet, ignores +.\" SO_INCOMING_CPU setting. .TP .B SO_KEEPALIVE Enable sending of keep-alive messages on connection-oriented sockets. |