From: Jiri Pirko <jiri@resnulli.us>
To: Shay Drory <shayd@nvidia.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
jiri@nvidia.com, saeedm@nvidia.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Moshe Shemesh <moshe@nvidia.com>
Subject: Re: [PATCH net-next v4 2/7] devlink: Add new "io_eq_size" generic device param
Date: Thu, 9 Dec 2021 12:16:21 +0100 [thread overview]
Message-ID: <YbHlhd0sFDwF5b6g@nanopsycho> (raw)
In-Reply-To: <20211209100929.28115-3-shayd@nvidia.com>
Thu, Dec 09, 2021 at 11:09:24AM CET, shayd@nvidia.com wrote:
>Add new device generic parameter to determine the size of the
>I/O completion EQs.
>
>For example, to reduce I/O EQ size to 64, execute:
>$ devlink dev param set pci/0000:06:00.0 \
> name io_eq_size value 64 cmode driverinit
>$ devlink dev reload pci/0000:06:00.0
>
>Signed-off-by: Shay Drory <shayd@nvidia.com>
>Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2021-12-09 11:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 10:09 [PATCH net-next v4 0/7] net/mlx5: Memory optimizations Shay Drory
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 [this message]
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=YbHlhd0sFDwF5b6g@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=shayd@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