lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 27 Sep 2014 09:50:54 -0700 From: Eric Dumazet <edumazet@...gle.com> To: "David S. Miller" <davem@...emloft.net> Cc: netdev@...r.kernel.org, Yuchung Cheng <ycheng@...gle.com>, Neal Cardwell <ncardwell@...gle.com>, Christoph Paasch <christoph.paasch@...ouvain.be>, Eric Dumazet <edumazet@...gle.com> Subject: [PATCH v4 net-next 0/3] tcp: better TCP_SKB_CB layout TCP had the assumption that IPCB and IP6CB are first members of skb->cb[] This is fine, except that IPCB/IP6CB are used in TCP for a very short time in input path. What really matters for TCP stack is to get skb->next, TCP_SKB_CB(skb)->seq, and TCP_SKB_CB(skb)->end_seq in the same cache line. skb that are immediately consumed do not care because whole skb->cb[] is hot in cpu cache, while skb that sit in wocket write queue or receive queues do not need TCP_SKB_CB(skb)->header at all. This patch set implements the prereq for IPv4, IPv6, and TCP to make this possible. This makes TCP more efficient. Eric Dumazet (3): ipv4: rename ip_options_echo to __ip_options_echo() ipv6: add a struct inet6_skb_parm param to ipv6_opt_accepted() tcp: better TCP_SKB_CB layout to reduce cache line misses include/net/ip.h | 15 ++++++++++++--- include/net/ipv6.h | 3 ++- include/net/tcp.h | 12 ++++++------ net/dccp/ipv6.c | 2 +- net/ipv4/ip_options.c | 6 ++---- net/ipv4/ip_output.c | 8 +++++--- net/ipv4/tcp_ipv4.c | 29 ++++++++++++++++++----------- net/ipv4/tcp_output.c | 5 +++++ net/ipv6/af_inet6.c | 4 ++-- net/ipv6/syncookies.c | 2 +- net/ipv6/tcp_ipv6.c | 12 ++++++++++-- 11 files changed, 64 insertions(+), 34 deletions(-) -- 2.1.0.rc2.206.gedb03e5 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists