[TCP]: tcp_memory_pressure and tcp_socket are__read_mostly candidates
authorEric Dumazet <dada1@cosmosbay.com>
Tue, 27 Mar 2007 20:58:31 +0000 (13:58 -0700)
committerDavid S. Miller <davem@sunset.davemloft.net>
Thu, 26 Apr 2007 05:28:19 +0000 (22:28 -0700)
commit4103f8cd5c1f260d674a7b426ed221812de54d47
tree28649757907dd77b53a8c16533c963c43fea4be0
parent73417f617a93cf30342c3ea41abc38927bd467aa
[TCP]: tcp_memory_pressure and tcp_socket are__read_mostly candidates

tcp_memory_pressure and tcp_socket currently share a cache line with tcp_memory_allocated, tcp_sockets_allocated.
(Very hot cache line)
It makes sense to declare these variables as __read_mostly, to avoid false sharing on SMP.

ffffffff8081d9c0 B tcp_orphan_count
ffffffff8081d9c4 B tcp_memory_allocated
ffffffff8081d9c8 B tcp_sockets_allocated
ffffffff8081d9cc B tcp_memory_pressure
ffffffff8081d9d0 b tcp_md5sig_users
ffffffff8081d9d8 b tcp_md5sig_pool
ffffffff8081d9e0 b warntime.31570
ffffffff8081d9e8 b tcp_socket

Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/tcp.c
net/ipv4/tcp_ipv4.c