thank you for your feedback. Following your guidance I studied the
inet_diag/tcp_diag kernel code for AF_INET sockets. It could make sense
to create an smc_diag module with an smc_diag_handler to provide
SMC-socket data to userspace. Userspace tools could exploit this by
receiving the SMC-socket data via AF_NETLINK sockets of protocol
Please let me know, if this is the right direction.
On 09/28/2016 04:27 AM, David Miller wrote:
> From: Ursula Braun <ubr...@linux.vnet.ibm.com>
> Date: Tue, 27 Sep 2016 18:41:56 +0200
>> Maintain a list of SMC sockets and display important SMC socket
>> information in /proc/net/smc.
>> Signed-off-by: Ursula Braun <ubr...@linux.vnet.ibm.com>
> Dumping internal tables and information via /procfs is strongly
> Please use a more modern mechanism (such as netlink) to expose this
> information to the user.
> You'll be most likely to succeed in your submission if you make use of
> or design a generic facility that allows other drivers similar to
> your's to provide this kind of information as well.
> I'm sorry if this is frustrating, but this is a huge piece of
> infrastructure, therefore you can expect lots of pieces to get
> feedback and require changes like this.