netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Saeed Mahameed <saeed@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
	Gal Pressman <gal@nvidia.com>,
	Leon Romanovsky <leonro@nvidia.com>,
	Hamdan Igbaria <hamdani@nvidia.com>,
	Yevgeny Kliteynik <kliteyn@nvidia.com>
Subject: Re: [net-next 13/15] net/mlx5: DR, Change SWS usage to debug fs seq_file interface
Date: Mon, 29 Jan 2024 20:55:29 +0000	[thread overview]
Message-ID: <20240129205529.GS401354@kernel.org> (raw)
In-Reply-To: <20240126223616.98696-14-saeed@kernel.org>

On Fri, Jan 26, 2024 at 02:36:14PM -0800, Saeed Mahameed wrote:
> From: Hamdan Igbaria <hamdani@nvidia.com>
> 
> In current SWS debug dump mechanism we implement the seq_file interface,
> but we only implement the 'show' callback to dump the whole steering DB
> with a single call to this callback.
> 
> However, for large data size the seq_printf function will fail to
> allocate a buffer with the adequate capacity to hold such data.
> 
> This patch solves this problem by utilizing the seq_file interface
> mechanism in the following way:
>  - when the user triggers a dump procedure, we will allocate a list of
>    buffers that hold the whole data dump (in the start callback)
>  - using the start, next, show and stop callbacks of the seq_file
>    API we iterate through the list and dump the whole data
> 
> Signed-off-by: Hamdan Igbaria <hamdani@nvidia.com>
> Reviewed-by: Yevgeny Kliteynik <kliteyn@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
> ---
>  .../mellanox/mlx5/core/steering/dr_dbg.c      | 726 ++++++++++++++----
>  .../mellanox/mlx5/core/steering/dr_dbg.h      |  20 +
>  2 files changed, 615 insertions(+), 131 deletions(-)
> 
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/steering/dr_dbg.c b/drivers/net/ethernet/mellanox/mlx5/core/steering/dr_dbg.c

...

> @@ -568,24 +927,41 @@ static int
>  dr_dump_domain_info_caps(struct seq_file *file, struct mlx5dr_cmd_caps *caps,
>  			 const u64 domain_id)
>  {
> +	char buff[MLX5DR_DEBUG_DUMP_BUFF_LENGTH];

...

Hi Saeed and Hamdan,

I am seeing some warnings which I think relate to stack usage like the above,
combined with inlining.

clang-17 W=1 build on x86_64 says:

 .../dr_dbg.c:1071:1: warning: stack frame size (2552) exceeds limit (2048) in 'dr_dump_start' [-Wframe-larger-than]
  1071 | dr_dump_start(struct seq_file *file, loff_t *pos)
       | ^
 .../dr_dbg.c:703:1: warning: stack frame size (2136) exceeds limit (2048) in 'dr_dump_matcher_rx_tx' [-Wframe-larger-than]
   703 | dr_dump_matcher_rx_tx(struct seq_file *file, bool is_rx,
       | ^

gcc-13 W=1 build on x86_64 says:

 .../dr_dbg.c: In function 'dr_dump_domain':
 .../dr_dbg.c:1044:1: warning: the frame size of 2096 bytes is larger than 2048 bytes [-Wframe-larger-than=]
  1044 | }
       | ^

> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/steering/dr_dbg.h b/drivers/net/ethernet/mellanox/mlx5/core/steering/dr_dbg.h
> index def6cf853eea..13511716cdbc 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/steering/dr_dbg.h
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/steering/dr_dbg.h
> @@ -1,10 +1,30 @@
>  /* SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB */
>  /* Copyright (c) 2021, NVIDIA CORPORATION & AFFILIATES. All rights reserved. */
>  
> +#define MLX5DR_DEBUG_DUMP_BUFF_SIZE (64 * 1024 * 1024)
> +#define MLX5DR_DEBUG_DUMP_BUFF_LENGTH 1024

...

  reply	other threads:[~2024-01-29 20:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 22:36 [pull request][net-next 00/15] mlx5 updates 2024-01-26 Saeed Mahameed
2024-01-26 22:36 ` [net-next 01/15] xfrm: generalize xdo_dev_state_update_curlft to allow statistics update Saeed Mahameed
2024-01-26 22:36 ` [net-next 02/15] xfrm: get global statistics from the offloaded device Saeed Mahameed
2024-01-26 22:36 ` [net-next 03/15] net/mlx5e: Connect mlx5 IPsec statistics with XFRM core Saeed Mahameed
2024-01-26 22:36 ` [net-next 04/15] net/mlx5e: Delete obsolete IPsec code Saeed Mahameed
2024-01-26 22:36 ` [net-next 05/15] Documentation: Fix counter name of mlx5 vnic reporter Saeed Mahameed
2024-01-26 22:36 ` [net-next 06/15] net/mlx5: Rename mlx5_sf_dev_remove Saeed Mahameed
2024-01-26 22:36 ` [net-next 07/15] net/mlx5: remove fw_fatal reporter dump option for non PF Saeed Mahameed
2024-01-26 22:36 ` [net-next 08/15] net/mlx5: remove fw " Saeed Mahameed
2024-01-26 22:36 ` [net-next 09/15] net/mlx5: SF, Stop waiting for FW as teardown was called Saeed Mahameed
2024-01-26 22:36 ` [net-next 10/15] net/mlx5: Return specific error code for timeout on wait_fw_init Saeed Mahameed
2024-01-26 22:36 ` [net-next 11/15] net/mlx5: Remove initial segmentation duplicate definitions Saeed Mahameed
2024-01-26 22:36 ` [net-next 12/15] net/mlx5: Change missing SyncE capability print to debug Saeed Mahameed
2024-01-26 22:36 ` [net-next 13/15] net/mlx5: DR, Change SWS usage to debug fs seq_file interface Saeed Mahameed
2024-01-29 20:55   ` Simon Horman [this message]
2024-01-31  1:42     ` Yevgeny Kliteynik
2024-01-26 22:36 ` [net-next 14/15] net/mlx5e: XSK, Exclude tailroom from non-linear SKBs memory calculations Saeed Mahameed
2024-01-26 22:36 ` [net-next 15/15] net/mlx5e: XDP, Exclude headroom and tailroom from " Saeed Mahameed

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=20240129205529.GS401354@kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=hamdani@nvidia.com \
    --cc=kliteyn@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeed@kernel.org \
    --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).