From: patchwork-bot+netdevbpf@kernel.org
To: Matteo Croce <technoboy85@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
shakeel.butt@linux.dev, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, teknoraver@meta.com
Subject: Re: [PATCH net-next v2 0/2] net: visibility of memory limits in netns
Date: Sat, 01 Jun 2024 23:20:29 +0000 [thread overview]
Message-ID: <171728402968.13922.4485290889430995702.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240530232722.45255-1-technoboy85@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 31 May 2024 01:27:20 +0200 you wrote:
> From: Matteo Croce <teknoraver@meta.com>
>
> Some programs need to know the size of the network buffers to operate
> correctly, export the following sysctls read-only in network namespaces:
>
> - net.core.rmem_default
> - net.core.rmem_max
> - net.core.wmem_default
> - net.core.wmem_max
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: make net.core.{r,w}mem_{default,max} namespaced
https://git.kernel.org/netdev/net-next/c/19249c0724f2
- [net-next,v2,2/2] selftests: net: tests net.core.{r,w}mem_{default,max} sysctls in a netns
https://git.kernel.org/netdev/net-next/c/5b5233fb81bf
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:[~2024-06-01 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 23:27 [PATCH net-next v2 0/2] net: visibility of memory limits in netns technoboy85
2024-05-30 23:27 ` [PATCH net-next v2 1/2] net: make net.core.{r,w}mem_{default,max} namespaced technoboy85
2024-05-31 8:12 ` Eric Dumazet
2024-05-31 22:11 ` Shakeel Butt
2024-05-30 23:27 ` [PATCH net-next v2 2/2] selftests: net: tests net.core.{r,w}mem_{default,max} sysctls in a netns technoboy85
2024-06-01 23:20 ` 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=171728402968.13922.4485290889430995702.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shakeel.butt@linux.dev \
--cc=shuah@kernel.org \
--cc=technoboy85@gmail.com \
--cc=teknoraver@meta.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).