From: Jakub Kicinski <kuba@kernel.org>
To: Michal Wilczynski <michal.wilczynski@intel.com>
Cc: netdev@vger.kernel.org, alexandr.lobakin@intel.com,
jacob.e.keller@intel.com, jesse.brandeburg@intel.com,
przemyslaw.kitszel@intel.com, anthony.l.nguyen@intel.com,
ecree.xilinx@gmail.com, jiri@resnulli.us
Subject: Re: [PATCH net-next v11 08/11] ice: Implement devlink-rate API
Date: Mon, 14 Nov 2022 21:11:37 -0800 [thread overview]
Message-ID: <20221114211137.2852a1fe@kernel.org> (raw)
In-Reply-To: <20221114173138.165319-9-michal.wilczynski@intel.com>
On Mon, 14 Nov 2022 18:31:35 +0100 Michal Wilczynski wrote:
> There is a need to support modification of Tx scheduler tree, in the
> ice driver. This will allow user to control Tx settings of each node in
> the internal hierarchy of nodes. As a result user will be able to use
> Hierarchy QoS implemented entirely in the hardware.
>
> This patch implemenents devlink-rate API. It also exports initial
> default hierarchy. It's mostly dictated by the fact that the tree
> can't be removed entirely, all we can do is enable the user to modify
> it. For example root node shouldn't ever be removed, also nodes that
> have children are off-limits.
drivers/net/ethernet/intel/ice/ice_devlink.c:794: warning: Function parameter or member 'bw' not described in 'ice_set_object_tx_share'
drivers/net/ethernet/intel/ice/ice_devlink.c:818: warning: Function parameter or member 'bw' not described in 'ice_set_object_tx_max'
drivers/net/ethernet/intel/ice/ice_devlink.c:842: warning: Function parameter or member 'priority' not described in 'ice_set_object_tx_priority'
drivers/net/ethernet/intel/ice/ice_devlink.c:871: warning: Function parameter or member 'weight' not described in 'ice_set_object_tx_weight'
Feel free to post a v12 with these fixed, I'll review the latest
tomorrow.
next prev parent reply other threads:[~2022-11-15 5:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 17:31 [PATCH net-next v11 00/11] Implement devlink-rate API and extend it Michal Wilczynski
2022-11-14 17:31 ` [PATCH net-next v11 01/11] devlink: Introduce new attribute 'tx_priority' to devlink-rate Michal Wilczynski
2022-11-14 17:31 ` [PATCH net-next v11 02/11] devlink: Introduce new attribute 'tx_weight' " Michal Wilczynski
2022-11-14 17:31 ` [PATCH net-next v11 03/11] devlink: Enable creation of the devlink-rate nodes from the driver Michal Wilczynski
2022-11-14 17:31 ` [PATCH net-next v11 04/11] devlink: Allow for devlink-rate nodes parent reassignment Michal Wilczynski
2022-11-14 17:31 ` [PATCH net-next v11 05/11] devlink: Allow to set up parent in devl_rate_leaf_create() Michal Wilczynski
2022-11-14 17:31 ` [PATCH net-next v11 06/11] ice: Introduce new parameters in ice_sched_node Michal Wilczynski
2022-11-14 17:31 ` [PATCH net-next v11 07/11] ice: Add an option to pre-allocate memory for ice_sched_node Michal Wilczynski
2022-11-14 17:31 ` [PATCH net-next v11 08/11] ice: Implement devlink-rate API Michal Wilczynski
2022-11-15 5:11 ` Jakub Kicinski [this message]
2022-11-14 17:31 ` [PATCH net-next v11 09/11] ice: Prevent ADQ, DCB coexistence with Custom Tx scheduler Michal Wilczynski
2022-11-14 17:31 ` [PATCH net-next v11 10/11] ice: Add documentation for devlink-rate implementation Michal Wilczynski
2022-11-14 17:31 ` [PATCH net-next v11 11/11] Documentation: Add documentation for new devlink-rate attributes Michal Wilczynski
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=20221114211137.2852a1fe@kernel.org \
--to=kuba@kernel.org \
--cc=alexandr.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=ecree.xilinx@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=michal.wilczynski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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).