From: <Daniel.Machon@microchip.com>
To: <bagasdotme@gmail.com>
Cc: <netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<saeedm@nvidia.com>, <leon@kernel.org>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<corbet@lwn.net>, <gal@nvidia.com>, <rrameshbabu@nvidia.com>,
<msanalla@nvidia.com>, <moshe@nvidia.com>, <tariqt@nvidia.com>,
<leonro@nvidia.com>
Subject: Re: [PATCH net v2 2/4] Documentation: net/mlx5: Use bullet and definition lists for vnic counters description
Date: Tue, 16 May 2023 19:18:13 +0000 [thread overview]
Message-ID: <ZGPW9BZajS3q33ki@DEN-LT-70577> (raw)
In-Reply-To: <20230510035415.16956-3-bagasdotme@gmail.com>
> Description of the vnic counters:
> -total_q_under_processor_handle: number of queues in an error state due to
> -an async error or errored command.
> -send_queue_priority_update_flow: number of QP/SQ priority/SL update
> -events.
> -cq_overrun: number of times CQ entered an error state due to an
> -overflow.
> -async_eq_overrun: number of times an EQ mapped to async events was
> -overrun.
> -comp_eq_overrun: number of times an EQ mapped to completion events was
> -overrun.
> -quota_exceeded_command: number of commands issued and failed due to quota
> -exceeded.
> -invalid_command: number of commands issued and failed dues to any reason
> -other than quota exceeded.
> -nic_receive_steering_discard: number of packets that completed RX flow
> -steering but were discarded due to a mismatch in flow table.
> +
> +- total_q_under_processor_handle
> + number of queues in an error state due to
> + an async error or errored command.
> +- send_queue_priority_update_flow
> + number of QP/SQ priority/SL update events.
> +- cq_overrun
> + number of times CQ entered an error state due to an overflow.
> +- async_eq_overrun
> + number of times an EQ mapped to async events was overrun.
> + comp_eq_overrun number of times an EQ mapped to completion events was
> + overrun.
> +- quota_exceeded_command
> + number of commands issued and failed due to quota exceeded.
> +- invalid_command
> + number of commands issued and failed dues to any reason other than quota
> + exceeded.
Hi Bagas,
nit: I think 'dues' should be 'due' here. Might as well get that in
when touching the code anyway.
Other than that:
Reviewed-by: Daniel Machon <daniel.machon@microchip.com>
> +- nic_receive_steering_discard
> + number of packets that completed RX flow
> + steering but were discarded due to a mismatch in flow table.
next prev parent reply other threads:[~2023-05-16 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 3:54 [PATCH net v2 0/4] Documentation fixes for Mellanox mlx5 devlink info Bagas Sanjaya
2023-05-10 3:54 ` [PATCH net v2 1/4] Documentation: net/mlx5: Wrap vnic reporter devlink commands in code blocks Bagas Sanjaya
2023-05-10 9:52 ` Simon Horman
2023-05-10 3:54 ` [PATCH net v2 2/4] Documentation: net/mlx5: Use bullet and definition lists for vnic counters description Bagas Sanjaya
2023-05-10 9:52 ` Simon Horman
2023-05-16 19:18 ` Daniel.Machon [this message]
2023-05-10 3:54 ` [PATCH net v2 3/4] Documentation: net/mlx5: Add blank line separator before numbered lists Bagas Sanjaya
2023-05-10 9:52 ` Simon Horman
2023-05-10 3:54 ` [PATCH net v2 4/4] Documentation: net/mlx5: Wrap notes in admonition blocks Bagas Sanjaya
2023-05-10 9:51 ` Simon Horman
2023-05-16 18:27 ` Jonathan Corbet
2023-05-16 13:29 ` [PATCH net v2 0/4] Documentation fixes for Mellanox mlx5 devlink info Bagas Sanjaya
2023-05-16 18:29 ` Jonathan Corbet
2023-05-16 22:37 ` Jakub Kicinski
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=ZGPW9BZajS3q33ki@DEN-LT-70577 \
--to=daniel.machon@microchip.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=moshe@nvidia.com \
--cc=msanalla@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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 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).