From: Karsten Graul <kgraul@linux.ibm.com>
To: David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Stefan Raspl <raspl@linux.ibm.com>,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
guvenc@linux.ibm.com
Subject: [PATCH net-next v2 0/4] net/smc: Add SMC statistic support
Date: Wed, 16 Jun 2021 16:52:54 +0200 [thread overview]
Message-ID: <20210616145258.2381446-1-kgraul@linux.ibm.com> (raw)
Please apply the following patch series for smc to netdev's net-next tree.
This v2 is a resend of the code contained in v1 but with an updated
cover letter to describe why we have chosen to use the generic netlink
mechanism to access the smc protocol's statistic data.
The patchset adds statistic support to the SMC protocol. Per-cpu
variables are used to collect the statistic information for better
performance and for reducing concurrency pitfalls. The code that is
collecting statistic data is implemented in macros to increase code
reuse and readability.
The generic netlink mechanism in SMC is extended to provide the
collected statistics to userspace.
Network namespace awareness is also part of the statistics
implementation.
SMC is a protocol interacting with PCI devices (like RoCE Cards) and
runs on top of the TCP protocol. As SMC is a network protocol and not
an ethernet device driver, we decided to use the generic netlink
interface. This should be comparable to what other protocols in the
net subsystem like tipc, ncsi, ieee802154 or tcp, et al, do.
There is already an established internal generic netlink interface
mechanism in SMC which is used to collect SMC Protocol internal
information. This patchset extends that existing mechanism.
Guvenc Gulce (4):
net/smc: Add SMC statistics support
net/smc: Add netlink support for SMC statistics
net/smc: Add netlink support for SMC fallback statistics
net/smc: Make SMC statistics network namespace aware
include/net/net_namespace.h | 4 +
include/net/netns/smc.h | 16 ++
include/uapi/linux/smc.h | 83 ++++++++
net/smc/Makefile | 2 +-
net/smc/af_smc.c | 102 +++++++--
net/smc/smc_core.c | 13 +-
net/smc/smc_netlink.c | 11 +
net/smc/smc_netlink.h | 2 +-
net/smc/smc_rx.c | 8 +
net/smc/smc_stats.c | 413 ++++++++++++++++++++++++++++++++++++
net/smc/smc_stats.h | 266 +++++++++++++++++++++++
net/smc/smc_tx.c | 18 +-
12 files changed, 917 insertions(+), 21 deletions(-)
create mode 100644 include/net/netns/smc.h
create mode 100644 net/smc/smc_stats.c
create mode 100644 net/smc/smc_stats.h
--
2.25.1
next reply other threads:[~2021-06-16 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 14:52 Karsten Graul [this message]
2021-06-16 14:52 ` [PATCH net-next v2 1/4] net/smc: Add SMC statistics support Karsten Graul
2021-06-16 14:52 ` [PATCH net-next v2 2/4] net/smc: Add netlink support for SMC statistics Karsten Graul
2021-06-16 14:52 ` [PATCH net-next v2 3/4] net/smc: Add netlink support for SMC fallback statistics Karsten Graul
2021-06-16 14:52 ` [PATCH net-next v2 4/4] net/smc: Make SMC statistics network namespace aware Karsten Graul
2021-06-16 20:10 ` [PATCH net-next v2 0/4] net/smc: Add SMC statistic support patchwork-bot+netdevbpf
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=20210616145258.2381446-1-kgraul@linux.ibm.com \
--to=kgraul@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=guvenc@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@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