From: Wen Gu <guwen@linux.alibaba.com>
To: kgraul@linux.ibm.com, wenjia@linux.ibm.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Cc: linux-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/2] Separate SMC parameter settings from TCP sysctls
Date: Tue, 20 Sep 2022 10:45:05 +0800 [thread overview]
Message-ID: <1663641907-15852-1-git-send-email-guwen@linux.alibaba.com> (raw)
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.
Tony Lu (1):
net/smc: Unbind r/w buffer size from clcsock and make them tunable
Wen Gu (1):
net/smc: Introduce a specific sysctl for TEST_LINK time
Documentation/networking/smc-sysctl.rst | 25 ++++++++++++++++++++++++
include/net/netns/smc.h | 3 +++
net/smc/af_smc.c | 5 ++---
net/smc/smc_core.c | 8 ++++----
net/smc/smc_llc.c | 2 +-
net/smc/smc_llc.h | 1 +
net/smc/smc_sysctl.c | 34 +++++++++++++++++++++++++++++++++
7 files changed, 70 insertions(+), 8 deletions(-)
--
1.8.3.1
next reply other threads:[~2022-09-20 2:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 2:45 Wen Gu [this message]
2022-09-20 2:53 ` [PATCH net-next 1/2] net/smc: Introduce a specific sysctl for TEST_LINK time Wen Gu
2022-09-20 2:57 ` Tony Lu
2022-09-20 4:55 ` dust.li
2022-09-20 6:23 ` Wen Gu
2022-09-20 8:21 ` dust.li
2022-09-20 9:03 ` Wen Gu
2022-09-20 2:54 ` [PATCH net-next 2/2] net/smc: Unbind r/w buffer size from clcsock and make them tunable Wen Gu
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=1663641907-15852-1-git-send-email-guwen@linux.alibaba.com \
--to=guwen@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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;
as well as URLs for NNTP newsgroup(s).