All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, dev@openvswitch.org, davem@davemloft.net,
	aconole@redhat.com, echaudro@redhat.com, edumazet@google.com,
	gal@nvidia.com, i.maximets@ovn.org, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org
Subject: Re: [PATCH net] openvswitch: Allocate struct ovs_pcpu_storage dynamically
Date: Tue, 17 Jun 2025 13:00:30 +0000	[thread overview]
Message-ID: <175016523077.3113934.3649305675066595449.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250613123629.-XSoQTCu@linutronix.de>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 13 Jun 2025 14:36:29 +0200 you wrote:
> PERCPU_MODULE_RESERVE defines the maximum size that can by used for the
> per-CPU data size used by modules. This is 8KiB.
> 
> Commit 035fcdc4d240c ("openvswitch: Merge three per-CPU structures into
> one") restructured the per-CPU memory allocation for the module and
> moved the separate alloc_percpu() invocations at module init time to a
> static per-CPU variable which is allocated by the module loader.
> 
> [...]

Here is the summary with links:
  - [net] openvswitch: Allocate struct ovs_pcpu_storage dynamically
    https://git.kernel.org/netdev/net/c/7b4ac12cc929

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



      parent reply	other threads:[~2025-06-17 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 12:36 [PATCH net] openvswitch: Allocate struct ovs_pcpu_storage dynamically Sebastian Andrzej Siewior
2025-06-16 22:09 ` Jakub Kicinski
2025-06-17  7:58   ` Sebastian Andrzej Siewior
2025-06-17  8:00   ` Gal Pressman
2025-06-17 11:31 ` [ovs-dev] " Aaron Conole
2025-06-17 13:00 ` 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=175016523077.3113934.3649305675066595449.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aconole@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=i.maximets@ovn.org \
    --cc=kuba@kernel.org \
    --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.