From: patchwork-bot+netdevbpf@kernel.org
To: Wen Gu <guwen@linux.alibaba.com>
Cc: kgraul@linux.ibm.com, wenjia@linux.ibm.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] Separate SMC parameter settings from TCP sysctls
Date: Thu, 22 Sep 2022 11:20:15 +0000 [thread overview]
Message-ID: <166384561563.30593.9422265694634089959.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1663667542-119851-1-git-send-email-guwen@linux.alibaba.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 20 Sep 2022 17:52:20 +0800 you wrote:
> SMC shares some sysctls with TCP, but considering the difference
> between these two protocols, it may not be very suitable for SMC
> to reuse TCP parameter settings in some cases, such as keepalive
> time or buffer size.
>
> So this patch set aims to introduce some SMC specific sysctls to
> independently and flexibly set the parameters that suit SMC.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net/smc: Introduce a specific sysctl for TEST_LINK time
https://git.kernel.org/netdev/net-next/c/77eee3251431
- [net-next,v2,2/2] net/smc: Unbind r/w buffer size from clcsock and make them tunable
https://git.kernel.org/netdev/net-next/c/0227f058aa29
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-09-22 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 9:52 [PATCH net-next v2 0/2] Separate SMC parameter settings from TCP sysctls Wen Gu
2022-09-20 9:52 ` [PATCH net-next v2 1/2] net/smc: Introduce a specific sysctl for TEST_LINK time Wen Gu
2022-09-20 9:52 ` [PATCH net-next v2 2/2] net/smc: Unbind r/w buffer size from clcsock and make them tunable Wen Gu
2022-09-20 14:00 ` [PATCH net-next v2 0/2] Separate SMC parameter settings from TCP sysctls Wenjia Zhang
2022-09-22 11: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=166384561563.30593.9422265694634089959.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wenjia@linux.ibm.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