All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Petr Machata <petrm@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>, <netdev@vger.kernel.org>
Cc: Ido Schimmel <idosch@nvidia.com>, Amit Cohen <amcohen@nvidia.com>,
	Danielle Ratson <danieller@nvidia.com>, <mlxsw@nvidia.com>
Subject: Re: [PATCH net-next 0/6] mlxsw: Add support of latency TLV
Date: Thu, 19 Jan 2023 17:18:04 -0800	[thread overview]
Message-ID: <45a806ca-ff78-255c-3ffd-32bf0bf76353@intel.com> (raw)
In-Reply-To: <cover.1674123673.git.petrm@nvidia.com>



On 1/19/2023 2:32 AM, Petr Machata wrote:
> Amit Cohen writes:
> 
> Ethernet Management Datagrams (EMADs) are Ethernet packets sent between
> the driver and device's firmware. They are used to pass various
> configurations to the device, but also to get events (e.g., port up)
> from it. After the Ethernet header, these packets are built in a TLV
> format.
> 
> This is the structure of EMADs:
> * Ethernet header
> * Operation TLV
> * String TLV (optional)
> * Latency TLV (optional)
> * Reg TLV
> * End TLV
> 
> The latency of each EMAD is measured by firmware. The driver can get the
> measurement via latency TLV which can be added to each EMAD. This TLV is
> optional, when EMAD is sent with this TLV, the EMAD's response will include
> the TLV and will contain the firmware measurement.
> 
> Add support for Latency TLV and use it by default for all EMADs (see
> more information in commit messages). The latency measurements can be
> processed using BPF program for example, to create a histogram and average
> of the latency per register. In addition, it is possible to measure the
> end-to-end latency, so then the latency of the software overhead can be
> calculated. This information can be useful to improve the driver
> performance.

...

> Patch set overview:
> Patches #1-#3 add support for querying MGIR, to know if string TLV and
> latency TLV are supported
> Patches #4-#5 add some relevant fields to support latency TLV
> Patch #6 adds support of latency TLV
> 
> Amit Cohen (6):
>    mlxsw: reg: Add TLV related fields to MGIR register
>    mlxsw: Enable string TLV usage according to MGIR output
>    mlxsw: core: Do not worry about changing 'enable_string_tlv' while
>      sending EMADs
>    mlxsw: emad: Add support for latency TLV
>    mlxsw: core: Define latency TLV fields
>    mlxsw: Add support of latency TLV

Looks ok to me.

Reviewed-by: Tony Nguyen <anthony.l.nguyen@intel.com>

>   drivers/net/ethernet/mellanox/mlxsw/core.c    | 108 ++++++++++++++----
>   drivers/net/ethernet/mellanox/mlxsw/core.h    |   2 -
>   drivers/net/ethernet/mellanox/mlxsw/emad.h    |   4 +
>   drivers/net/ethernet/mellanox/mlxsw/reg.h     |  12 ++
>   .../net/ethernet/mellanox/mlxsw/spectrum.c    |   1 -
>   5 files changed, 103 insertions(+), 24 deletions(-)
> 

  parent reply	other threads:[~2023-01-20  1:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 10:32 [PATCH net-next 0/6] mlxsw: Add support of latency TLV Petr Machata
2023-01-19 10:32 ` [PATCH net-next 1/6] mlxsw: reg: Add TLV related fields to MGIR register Petr Machata
2023-01-19 10:32 ` [PATCH net-next 2/6] mlxsw: Enable string TLV usage according to MGIR output Petr Machata
2023-01-19 10:32 ` [PATCH net-next 3/6] mlxsw: core: Do not worry about changing 'enable_string_tlv' while sending EMADs Petr Machata
2023-01-19 10:32 ` [PATCH net-next 4/6] mlxsw: emad: Add support for latency TLV Petr Machata
2023-01-19 10:32 ` [PATCH net-next 5/6] mlxsw: core: Define latency TLV fields Petr Machata
2023-01-19 10:32 ` [PATCH net-next 6/6] mlxsw: Add support of latency TLV Petr Machata
2023-01-20  1:18 ` Tony Nguyen [this message]
2023-01-21  3:00 ` [PATCH net-next 0/6] " patchwork-bot+netdevbpf

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=45a806ca-ff78-255c-3ffd-32bf0bf76353@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=amcohen@nvidia.com \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.