Thread (21 messages) 21 messages, 6 authors, 2023-12-04

Re: [PATCH v8 net-next 0/5] Analyze and Reorganize core Networking Structs to optimize cacheline consumption

From: Neal Cardwell <ncardwell@google.com>
Date: 2023-12-02 22:36:29

On Sat, Dec 2, 2023 at 5:30 PM [off-list ref] wrote:
Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller [off-list ref]:

On Wed, 29 Nov 2023 07:27:51 +0000 you wrote:
quoted
Currently, variable-heavy structs in the networking stack is organized
chronologically, logically and sometimes by cacheline access.

This patch series attempts to reorganize the core networking stack
variables to minimize cacheline consumption during the phase of data
transfer. Specifically, we looked at the TCP/IP stack and the fast
path definition in TCP.

[...]
Here is the summary with links:
  - [v8,net-next,1/5] Documentations: Analyze heavily used Networking related structs
    https://git.kernel.org/netdev/net-next/c/14006f1d8fa2
  - [v8,net-next,2/5] cache: enforce cache groups
    https://git.kernel.org/netdev/net-next/c/aeb9ce058d7c
  - [v8,net-next,3/5] netns-ipv4: reorganize netns_ipv4 fast path variables
    https://git.kernel.org/netdev/net-next/c/18fd64d25422
  - [v8,net-next,4/5] net-device: reorganize net_device fast path variables
    (no matching commit)
  - [v8,net-next,5/5] tcp: reorganize tcp_sock fast path variables
    (no matching commit)
Both from this email and the git logs it looks like the last two
commits didn't make it in?  Is that intentional? :-)

cheers,
neal
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help