netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guvenc Gulce <guvenc@linux.ibm.com>
To: David Miller <davem@davemloft.net>, kgraul@linux.ibm.com
Cc: kuba@kernel.org, hca@linux.ibm.com, raspl@linux.ibm.com,
	netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] net/smc: Add SMC statistic support
Date: Tue, 8 Jun 2021 10:59:22 +0200	[thread overview]
Message-ID: <1df10dbb-a3bd-9b8f-6fb9-8a8fe98ae175@linux.ibm.com> (raw)
In-Reply-To: <20210607.133346.155691512247470187.davem@davemloft.net>

Hi Dave,
Thank you for looking into this. SMC is a protocol interacting with PCI devices (like RoCE Cards) and
runs on top of TCP protocol. As SMC is a network protocol and not an ethernet device driver, we
decided to use the generic netlink interface. 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.
Ethtool's predefined netlink interfaces are specifically tailored for the ethernet device internals and needs
and these netlink interfaces wouldn't really fit to the use cases of the SMC protocol.

Other protocols (like tipc, ncsi, ieee802154, tcp metrics) under the net subsystem use also similar generic
netlink mechanism for collecting and transporting protocol specific information to userspace. This also
encouraged us to make the generic netlink decision for exposing the gathered SMC protocol statistics
and internal information to the userspace.

Regards,

Guvenc Gulce

On 07/06/2021 22:33, David Miller wrote:
> From: Karsten Graul <kgraul@linux.ibm.com>
> Date: Mon,  7 Jun 2021 20:20:10 +0200
>
>> Please apply the following patch series for smc to netdev's net-next tree.
>>
>> 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.
> Why not use ethtool stats?
>
> Thank you.


  reply	other threads:[~2021-06-08  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 18:20 [PATCH net-next 0/4] net/smc: Add SMC statistic support Karsten Graul
2021-06-07 18:20 ` [PATCH net-next 1/4] net/smc: Add SMC statistics support Karsten Graul
2021-06-07 18:20 ` [PATCH net-next 2/4] net/smc: Add netlink support for SMC statistics Karsten Graul
2021-06-07 18:20 ` [PATCH net-next 3/4] net/smc: Add netlink support for SMC fallback statistics Karsten Graul
2021-06-07 18:20 ` [PATCH net-next 4/4] net/smc: Make SMC statistics network namespace aware Karsten Graul
2021-06-07 20:33 ` [PATCH net-next 0/4] net/smc: Add SMC statistic support David Miller
2021-06-08  8:59   ` Guvenc Gulce [this message]
2021-06-11  9:28     ` Karsten Graul

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=1df10dbb-a3bd-9b8f-6fb9-8a8fe98ae175@linux.ibm.com \
    --to=guvenc@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=hca@linux.ibm.com \
    --cc=kgraul@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;
as well as URLs for NNTP newsgroup(s).