netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Adam Li <adamli@os.amperecomputing.com>
Cc: corbet@lwn.net, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, willemb@google.com,
	yangtiezhu@loongson.cn, atenart@kernel.org, kuniyu@amazon.com,
	wuyun.abel@bytedance.com, leitao@debian.org,
	alexander@mihalicyn.com, dhowells@redhat.com, paulmck@kernel.org,
	joel.granados@gmail.com, urezki@gmail.com,
	joel@joelfernandes.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	patches@amperecomputing.com, cl@os.amperecomputing.com,
	shijie@os.amperecomputing.com
Subject: Re: [PATCH] net: make SK_MEMORY_PCPU_RESERV tunable
Date: Wed, 28 Feb 2024 09:30:30 +0000	[thread overview]
Message-ID: <170911263080.1645.11640647793580048759.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240226022452.20558-1-adamli@os.amperecomputing.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Mon, 26 Feb 2024 02:24:52 +0000 you wrote:
> This patch adds /proc/sys/net/core/mem_pcpu_rsv sysctl file,
> to make SK_MEMORY_PCPU_RESERV tunable.
> 
> Commit 3cd3399dd7a8 ("net: implement per-cpu reserves for
> memory_allocated") introduced per-cpu forward alloc cache:
> 
> "Implement a per-cpu cache of +1/-1 MB, to reduce number
> of changes to sk->sk_prot->memory_allocated, which
> would otherwise be cause of false sharing."
> 
> [...]

Here is the summary with links:
  - net: make SK_MEMORY_PCPU_RESERV tunable
    https://git.kernel.org/netdev/net-next/c/12a686c2e761

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-02-28  9:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26  2:24 [PATCH] net: make SK_MEMORY_PCPU_RESERV tunable Adam Li
2024-02-26 16:01 ` Lameter, Christopher
2024-02-27 20:38 ` Eric Dumazet
2024-02-27 23:08   ` Lameter, Christopher
2024-02-28  1:13     ` Jakub Kicinski
2024-02-28  9:32     ` Eric Dumazet
2024-02-28 13:23   ` Adam Li
2024-02-28 13:46     ` Eric Dumazet
2024-03-06 17:01       ` Lameter, Christopher
2024-03-06 17:28         ` Eric Dumazet
2024-02-28  9: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=170911263080.1645.11640647793580048759.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=adamli@os.amperecomputing.com \
    --cc=alexander@mihalicyn.com \
    --cc=atenart@kernel.org \
    --cc=cl@os.amperecomputing.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=joel.granados@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=leitao@debian.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=patches@amperecomputing.com \
    --cc=paulmck@kernel.org \
    --cc=shijie@os.amperecomputing.com \
    --cc=urezki@gmail.com \
    --cc=willemb@google.com \
    --cc=wuyun.abel@bytedance.com \
    --cc=yangtiezhu@loongson.cn \
    /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).