From: Wen Gu <guwen@linux.alibaba.com>
To: Wenjia Zhang <wenjia@linux.ibm.com>,
kgraul@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-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next] net/smc: Introduce SMC-related proc files
Date: Wed, 13 Sep 2023 17:53:57 +0800 [thread overview]
Message-ID: <a0a4567e-07f1-91db-50cb-bbfc803f5969@linux.alibaba.com> (raw)
In-Reply-To: <2b1d129c-06e2-0161-7c8a-1e930150d797@linux.ibm.com>
On 2023/9/11 19:54, Wenjia Zhang wrote:
>
>
>
> Hi Wen,
>
> I can understand your problem and frustration. However, there are two reasons I'm not really convinced by the proc file
> method:
> 1) AFAI, the proc method could consume many CPU time especially in case with a log of sockets to read the pseudo files.
> 2) We have already implemented the complex netlink method on the same purpose. I see the double expense to main the code.
>
> Then the question is if the lack of dependency issue can be handle somehow, or the proc method is the only way to
> achieve this purpose?
>
> Any opinion is welcome!
>
> Thanks,
> Wenjia
Hi, Wenjia. I agree with your concerns.
My initial intention is to make these proc files serve as a supplement to netlink to conveniently
check smc connections in an environment where smc-tools cannot be easily obtained.
Yes, proc files won't be the first choice for diagnosis, but can be a convenient backup.
Thanks,
Wen Gu
next prev parent reply other threads:[~2023-09-13 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 7:20 [RFC PATCH net-next] net/smc: Introduce SMC-related proc files Wen Gu
2023-09-11 11:54 ` Wenjia Zhang
2023-09-13 9:53 ` Wen Gu [this message]
2023-09-14 10:29 ` Alexandra Winter
2023-09-15 1:58 ` 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=a0a4567e-07f1-91db-50cb-bbfc803f5969@linux.alibaba.com \
--to=guwen@linux.alibaba.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jaka@linux.ibm.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=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