[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<171741362931.21322.15314690362780882616.git-patchwork-notify@kernel.org>
Date: Mon, 03 Jun 2024 11:20:29 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Guangguan Wang <guangguan.wang@...ux.alibaba.com>
Cc: wenjia@...ux.ibm.com, jaka@...ux.ibm.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
kgraul@...ux.ibm.com, alibuda@...ux.alibaba.com, tonylu@...ux.alibaba.com,
guwen@...ux.alibaba.com, linux-s390@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net/smc: Change the upper boundary of SMC-R's
snd_buf and rcv_buf to 512MB
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:
On Mon, 3 Jun 2024 11:00:17 +0800 you wrote:
> SMCR_RMBE_SIZES is the upper boundary of SMC-R's snd_buf and rcv_buf.
> The maximum bytes of snd_buf and rcv_buf can be calculated by 2^SMCR_
> RMBE_SIZES * 16KB. SMCR_RMBE_SIZES = 5 means the upper boundary is 512KB.
> TCP's snd_buf and rcv_buf max size is configured by net.ipv4.tcp_w/rmem[2]
> whose default value is 4MB or 6MB, is much larger than SMC-R's upper
> boundary.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net/smc: set rmb's SG_MAX_SINGLE_ALLOC limitation only when CONFIG_ARCH_NO_SG_CHAIN is defined
https://git.kernel.org/netdev/net-next/c/3ac14b9dfbd3
- [net-next,v2,2/2] net/smc: change SMCR_RMBE_SIZES from 5 to 15
https://git.kernel.org/netdev/net-next/c/2f4b101c542e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists