From: Ursula Braun <ubraun@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
utz.bacher@de.ibm.com
Subject: Re: [PATCH V2 net-next 15/15] smc: proc-fs interface for smc connections
Date: Wed, 12 Oct 2016 16:00:27 +0200 [thread overview]
Message-ID: <a02646ea-9f36-85fc-f761-fd6ed123051c@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160927.222741.584893707513031004.davem@davemloft.net>
Hi Dave,
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
NETLINK_SOCK_DIAG.
Please let me know, if this is the right direction.
Regards, Ursula
On 09/28/2016 04:27 AM, David Miller wrote:
> From: Ursula Braun <ubraun@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 <ubraun@linux.vnet.ibm.com>
>
> Dumping internal tables and information via /procfs is strongly
> deprecated.
>
> 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.
>
>
prev parent reply other threads:[~2016-10-12 14:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 16:41 [PATCH V2 net-next 00/15] net/smc: Shared Memory Communications - RDMA Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 01/15] net: introduce keepalive function in struct proto Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 02/15] smc: establish new socket family Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 03/15] smc: establish pnet table management Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 04/15] smc: introduce SMC as an IB-client Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 05/15] smc: CLC handshake (incl. preparation steps) Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 06/15] smc: connection and link group creation Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 07/15] smc: remote memory buffers (RMBs) Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 08/15] smc: work request (WR) base for use by LLC and CDC Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 09/15] smc: initialize IB transport incl. PD, MR, QP, CQ, event, WR Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 10/15] smc: link layer control (LLC) Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 11/15] smc: connection data control (CDC) Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 12/15] smc: send data (through RDMA) Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 13/15] smc: receive data from RMBE Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 14/15] smc: socket closing and linkgroup cleanup Ursula Braun
2016-09-27 16:41 ` [PATCH V2 net-next 15/15] smc: proc-fs interface for smc connections Ursula Braun
2016-09-28 2:27 ` David Miller
2016-10-12 14:00 ` Ursula Braun [this message]
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=a02646ea-9f36-85fc-f761-fd6ed123051c@linux.vnet.ibm.com \
--to=ubraun@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=utz.bacher@de.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