History

net: introduce SO_INCOMING_CPU

Alternative to RPS/RFS is to use hardware support for multiple queues. Then split a set of million of sockets into worker threads, each one using epoll() to manage events on its own socket pool. Ideally, we want one thread per RX/TX queue/cpu, but we have no way to know after accept() or connect() on which queue/cpu a socket is managed. We normally use one cpu per RX queue (IRQ smp_affinity being properly set), so remembering on socket structure which cpu delivered last packet is enough to solve the problem. After accept(), connect(), or even file descriptor passing around processes, applications can use : int cpu; socklen_t len = sizeof(cpu); getsockopt(fd, SOL_SOCKET, SO_INCOMING_CPU, &cpu, &len); And use this information to put the socket into the right silo for optimal performance, as all networking stack should run on the appropriate cpu, without need to send IPI (RPS/RFS).

Eric Dumazet committed 12 years ago

Commit 2c8c56e1 parent 3d9737921 files · +52 −2Browse files

Showing the changes to include/uapi (1 of 21 files). Show all

Unified · Split

include/uapi/asm-generic/socket.h+2−0
@@ -82,4 +82,6 @@ · 81 unmodified lines
8282
8383 #define SO_BPF_EXTENSIONS 48
8484
85+#define SO_INCOMING_CPU 49
86+
8587 #endif /* __ASM_GENERIC_SOCKET_H */

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t