From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, mptcp@lists.linux.dev, dsahern@kernel.org,
mathew.j.martineau@linux.intel.com, matthieu.baerts@tessares.net,
kuniyu@amazon.com
Subject: Re: [PATCH net-next v2 0/2] udp: avoid false sharing on receive
Date: Mon, 24 Oct 2022 10:30:19 +0000 [thread overview]
Message-ID: <166660741981.18313.518994743736905929.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1666287924.git.pabeni@redhat.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 20 Oct 2022 19:48:50 +0200 you wrote:
> Under high UDP load, the BH processing and the user-space receiver can
> run on different cores.
>
> The UDP implementation does a lot of effort to avoid false sharing in
> the receive path, but recent changes to the struct sock layout moved
> the sk_forward_alloc and the sk_rcvbuf fields on the same cacheline:
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: introduce and use custom sockopt socket flag
https://git.kernel.org/netdev/net-next/c/a5ef058dc4d9
- [net-next,v2,2/2] udp: track the forward memory release threshold in an hot cacheline
https://git.kernel.org/netdev/net-next/c/8a3854c7b8e4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-10-24 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 17:48 [PATCH net-next v2 0/2] udp: avoid false sharing on receive Paolo Abeni
2022-10-20 17:48 ` [PATCH net-next v2 1/2] net: introduce and use custom sockopt socket flag Paolo Abeni
2022-10-20 18:11 ` Eric Dumazet
2022-10-20 18:19 ` Kuniyuki Iwashima
2022-10-20 17:48 ` [PATCH net-next v2 2/2] udp: track the forward memory release threshold in an hot cacheline Paolo Abeni
2022-10-20 18:10 ` Eric Dumazet
2022-10-20 18:20 ` Kuniyuki Iwashima
2022-10-20 21:14 ` udp: track the forward memory release threshold in an hot cacheline: Tests Results MPTCP CI
2022-10-24 10:30 ` patchwork-bot+netdevbpf [this message]
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=166660741981.18313.518994743736905929.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.