From: shaozhengchao <shaozhengchao@huawei.com>
To: Wen Gu <guwen@linux.alibaba.com>, <wenjia@linux.ibm.com>,
<jaka@linux.ibm.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>
Cc: <alibuda@linux.alibaba.com>, <tonylu@linux.alibaba.com>,
<linux-kernel@vger.kernel.org>, <linux-s390@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/2] net/smc: introduce ringbufs usage statistics
Date: Tue, 6 Aug 2024 11:52:55 +0800 [thread overview]
Message-ID: <7f2decb7-3f32-1501-91db-c6b0da6baf37@huawei.com> (raw)
In-Reply-To: <20240805090551.80786-1-guwen@linux.alibaba.com>
Hi Wen Gu:
Your patchset looks fine. However, the current smc-tools tool is not
supported, so will you update the smc-tools tool?
Thank you
Zhengchao Shao
On 2024/8/5 17:05, Wen Gu wrote:
> Currently, we have histograms that show the sizes of ringbufs that ever
> used by SMC connections. However, they are always incremental and since
> SMC allows the reuse of ringbufs, we cannot know the actual amount of
> ringbufs being allocated or actively used.
>
> So this patch set introduces statistics for the amount of ringbufs that
> actually allocated by link group and actively used by connections of a
> certain net namespace, so that we can react based on these memory usage
> information, e.g. active fallback to TCP.
>
> With appropriate adaptations of smc-tools, we can obtain these ringbufs
> usage information:
>
> $ smcr -d linkgroup
> LG-ID : 00000500
> LG-Role : SERV
> LG-Type : ASYML
> VLAN : 0
> PNET-ID :
> Version : 1
> Conns : 0
> Sndbuf : 12910592 B <-
> RMB : 12910592 B <-
>
> or
>
> $ smcr -d stats
> [...]
> RX Stats
> Data transmitted (Bytes) 869225943 (869.2M)
> Total requests 18494479
> Buffer usage (Bytes) 12910592 (12.31M) <-
> [...]
>
> TX Stats
> Data transmitted (Bytes) 12760884405 (12.76G)
> Total requests 36988338
> Buffer usage (Bytes) 12910592 (12.31M) <-
> [...]
> [...]
>
> Wen Gu (2):
> net/smc: introduce statistics for allocated ringbufs of link group
> net/smc: introduce statistics for ringbufs usage of net namespace
>
> include/uapi/linux/smc.h | 6 ++++
> net/smc/smc_core.c | 74 ++++++++++++++++++++++++++++++++++------
> net/smc/smc_core.h | 2 ++
> net/smc/smc_stats.c | 8 +++++
> net/smc/smc_stats.h | 27 ++++++++++-----
> 5 files changed, 97 insertions(+), 20 deletions(-)
>
next prev parent reply other threads:[~2024-08-06 3:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 9:05 [PATCH net-next 0/2] net/smc: introduce ringbufs usage statistics Wen Gu
2024-08-05 9:05 ` [PATCH net-next 1/2] net/smc: introduce statistics for allocated ringbufs of link group Wen Gu
2024-08-06 10:49 ` Simon Horman
2024-08-06 12:23 ` Wen Gu
2024-08-05 9:05 ` [PATCH net-next 2/2] net/smc: introduce statistics for ringbufs usage of net namespace Wen Gu
2024-08-06 10:49 ` Simon Horman
2024-08-06 13:07 ` Wen Gu
2024-08-06 15:26 ` Simon Horman
2024-08-06 3:52 ` shaozhengchao [this message]
2024-08-06 11:54 ` [PATCH net-next 0/2] net/smc: introduce ringbufs usage statistics 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=7f2decb7-3f32-1501-91db-c6b0da6baf37@huawei.com \
--to=shaozhengchao@huawei.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@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=tonylu@linux.alibaba.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