netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neal Cardwell <ncardwell@google.com>
To: patchwork-bot+netdevbpf@kernel.org,
	 "David S. Miller" <davem@davemloft.net>
Cc: Coco Li <lixiaoyan@google.com>,
	kuba@kernel.org, edumazet@google.com,  mubashirq@google.com,
	pabeni@redhat.com, andrew@lunn.ch, corbet@lwn.net,
	 dsahern@kernel.org, daniel@iogearbox.net,
	netdev@vger.kernel.org,  wwchao@google.com, weiwan@google.com,
	pnemavat@google.com
Subject: Re: [PATCH v8 net-next 0/5] Analyze and Reorganize core Networking Structs to optimize cacheline consumption
Date: Sat, 2 Dec 2023 17:36:10 -0500	[thread overview]
Message-ID: <CADVnQymKa65a7O=YHqbjm3042+HusyP2t0m_ocf6RXkaRTwjnw@mail.gmail.com> (raw)
In-Reply-To: <170155622408.27182.16031150060782175153.git-patchwork-notify@kernel.org>

On Sat, Dec 2, 2023 at 5:30 PM <patchwork-bot+netdevbpf@kernel.org> wrote:
>
> Hello:
>
> This series was applied to netdev/net-next.git (main)
> by David S. Miller <davem@davemloft.net>:
>
> On Wed, 29 Nov 2023 07:27:51 +0000 you wrote:
> > 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

  reply	other threads:[~2023-12-02 22:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29  7:27 [PATCH v8 net-next 0/5] Analyze and Reorganize core Networking Structs to optimize cacheline consumption Coco Li
2023-11-29  7:27 ` [PATCH v8 net-next 1/5] Documentations: Analyze heavily used Networking related structs Coco Li
2023-11-30 10:37   ` Eric Dumazet
2023-12-02 20:00   ` Shakeel Butt
2023-11-29  7:27 ` [PATCH v8 net-next 2/5] cache: enforce cache groups Coco Li
2023-11-30 10:40   ` Eric Dumazet
2023-12-02  4:20   ` Jakub Kicinski
2023-12-02 20:08   ` Shakeel Butt
2023-11-29  7:27 ` [PATCH v8 net-next 3/5] netns-ipv4: reorganize netns_ipv4 fast path variables Coco Li
2023-11-30 10:48   ` Eric Dumazet
2023-12-02 20:23   ` Shakeel Butt
2023-11-29  7:27 ` [PATCH v8 net-next 4/5] net-device: reorganize net_device " Coco Li
2023-11-30 10:49   ` Eric Dumazet
2023-12-02 20:28   ` Shakeel Butt
2023-11-29  7:27 ` [PATCH v8 net-next 5/5] tcp: reorganize tcp_sock " Coco Li
2023-11-30 10:52   ` Eric Dumazet
2023-12-02 20:31   ` Shakeel Butt
2023-12-02 20:34 ` [PATCH v8 net-next 0/5] Analyze and Reorganize core Networking Structs to optimize cacheline consumption Shakeel Butt
2023-12-02 22:30 ` patchwork-bot+netdevbpf
2023-12-02 22:36   ` Neal Cardwell [this message]
2023-12-04 19:06     ` Jakub Kicinski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADVnQymKa65a7O=YHqbjm3042+HusyP2t0m_ocf6RXkaRTwjnw@mail.gmail.com' \
    --to=ncardwell@google.com \
    --cc=andrew@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=lixiaoyan@google.com \
    --cc=mubashirq@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=patchwork-bot+netdevbpf@kernel.org \
    --cc=pnemavat@google.com \
    --cc=weiwan@google.com \
    --cc=wwchao@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).