public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shay Drory <shayd@nvidia.com>
To: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Cc: jiri@nvidia.com, saeedm@nvidia.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, Shay Drory <shayd@nvidia.com>
Subject: [PATCH net-next v4 0/7] net/mlx5: Memory optimizations
Date: Thu,  9 Dec 2021 12:09:22 +0200	[thread overview]
Message-ID: <20211209100929.28115-1-shayd@nvidia.com> (raw)

This series provides knobs which will enable users to
minimize memory consumption of mlx5 Functions (PF/VF/SF).
mlx5 exposes two new generic devlink params for EQ size
configuration and uses devlink generic param max_macs.

Patches summary:
 - Patch-1 Introduce log_max_current_uc_list_wr_supported bit 
 - Patches-2-3 Provides I/O EQ size param which enables to save
   up to 128KB.
 - Patches-4-5 Provides event EQ size param which enables to save
   up to 512KB.
 - Patch-6 Clarify max_macs param.
 - Patch-7 Provides max_macs param which enables to save up to 70KB

In total, this series can save up to 700KB per Function.

---
changelog:
v3->v4:
- align devlink_param doc of EQ size params to u32.
v2->v3:
- change type of EQ size params to u32 per Jiri suggestion.
- separate ifc changes to new patch
v1->v2:
- convert io_eq_size and event_eq_size from devlink_resources to
  generic devlink_params

Shay Drory (7):
  net/mlx5: Introduce log_max_current_uc_list_wr_supported bit
  devlink: Add new "io_eq_size" generic device param
  net/mlx5: Let user configure io_eq_size param
  devlink: Add new "event_eq_size" generic device param
  net/mlx5: Let user configure event_eq_size param
  devlink: Clarifies max_macs generic devlink param
  net/mlx5: Let user configure max_macs generic param

 .../networking/devlink/devlink-params.rst     | 12 ++-
 Documentation/networking/devlink/mlx5.rst     | 10 +++
 .../net/ethernet/mellanox/mlx5/core/devlink.c | 88 +++++++++++++++++++
 drivers/net/ethernet/mellanox/mlx5/core/eq.c  | 34 ++++++-
 .../net/ethernet/mellanox/mlx5/core/main.c    | 21 +++++
 include/linux/mlx5/mlx5_ifc.h                 |  2 +-
 include/net/devlink.h                         |  8 ++
 net/core/devlink.c                            | 10 +++
 8 files changed, 180 insertions(+), 5 deletions(-)

-- 
2.21.3


             reply	other threads:[~2021-12-09 10:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 10:09 Shay Drory [this message]
2021-12-09 10:09 ` [PATCH net-next v4 1/7] net/mlx5: Introduce log_max_current_uc_list_wr_supported bit Shay Drory
2021-12-09 10:09 ` [PATCH net-next v4 2/7] devlink: Add new "io_eq_size" generic device param Shay Drory
2021-12-09 11:16   ` Jiri Pirko
2021-12-09 10:09 ` [PATCH net-next v4 3/7] net/mlx5: Let user configure io_eq_size param Shay Drory
2021-12-09 10:09 ` [PATCH net-next v4 4/7] devlink: Add new "event_eq_size" generic device param Shay Drory
2021-12-09 11:16   ` Jiri Pirko
2021-12-09 10:09 ` [PATCH net-next v4 5/7] net/mlx5: Let user configure event_eq_size param Shay Drory
2021-12-09 10:09 ` [PATCH net-next v4 6/7] devlink: Clarifies max_macs generic devlink param Shay Drory
2021-12-09 10:09 ` [PATCH net-next v4 7/7] net/mlx5: Let user configure max_macs generic param Shay Drory

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=20211209100929.28115-1-shayd@nvidia.com \
    --to=shayd@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@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