From: "Wilczynski, Michal" <michal.wilczynski@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next v6 4/4] ice: Add txbalancing devlink param
Date: Thu, 21 Jul 2022 16:46:31 +0200 [thread overview]
Message-ID: <97f5dd9e-b2f4-2a22-2ef7-9daabb70cb05@intel.com> (raw)
In-Reply-To: <92cab6fd-c6b4-6834-74f0-8df5a10ccbcb@intel.com>
On 7/21/2022 1:17 AM, Tony Nguyen wrote:
>
>
> On 7/20/2022 7:40 AM, Michal Wilczynski wrote:
>> From: Lukasz Czapnik <lukasz.czapnik@intel.com>
>>
>> It was observed that Tx performance was inconsistent across all queues
>> and/or VSIs and that it was directly connected to existing 9-layer
>> topology of the Tx scheduler.
>>
>> Introduce new private devlink param - txbalance. This paramerer gives
>> user
>
> s/paramerer/parameter
>
>> flexibility to choose the 5-layer transmit scheduler topology which
>> helps
>> to smooth out the transmit performance.
>>
>> Allowed parameter values are true for enabled and false for disabled.
>
> Please document these in Documentation/networking/devlink/ice.rst
>
>> Example usage:
>>
>> Show:
>> devlink dev param show pci/0000:4b:00.0 name txbalancing
>> pci/0000:4b:00.0:
>> name txbalancing type driver-specific
>> values:
>> cmode permanent value true
>>
>> Set:
>> devlink dev param set pci/0000:4b:00.0 name txbalancing value true cmode
>> permanent
>>
>> Signed-off-by: Lukasz Czapnik <lukasz.czapnik@intel.com>
>> Signed-off-by: Michal Wilczynski <michal.wilczynski@intel.com>
>
> <snip>
>
>> +/**
>> + * ice_devlink_txbalance_get - Get txbalance parameter
>> + * @devlink: pointer to the devlink instance
>> + * @id: the parameter ID to set
>> + * @ctx: context to store the parameter value
>> + *
>> + * Returns zero on success and negative value on failure.
>> + */
>> +static int ice_devlink_txbalance_get(struct devlink *devlink, u32 id,
>> + struct devlink_param_gset_ctx *ctx)
>
> nit: Can you use GNU style on these
>
> static int
> ice_devlink_txbalance_get(...)
>
>
>> +{
>> + struct ice_pf *pf = devlink_priv(devlink);
>> + struct device *dev = ice_pf_to_dev(pf);
>> + int status;
>> +
>> + status = ice_get_tx_topo_user_sel(pf, &ctx->val.vbool);
>> + if (status) {
>> + dev_warn(dev, "Failed to read Tx Scheduler Tree - User
>> Selection data from flash\n");
>> + return -EIO;
>> + }
>> +
>> + return 0;
>> +}
>> +
>
> As well as the lkp reported issues[1]
>
> [1]
> https://lore.kernel.org/intel-wired-lan/202207210108.7ZpVcgDQ-lkp@intel.com/
Okay thank you, fixed issues and submitted a new version
BR,
Michał
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-07-21 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 14:40 [Intel-wired-lan] [PATCH net-next v6 0/4] ice: Support 5 layer tx scheduler topology Michal Wilczynski
2022-07-20 14:40 ` [Intel-wired-lan] [PATCH net-next v6 1/4] ice: Support 5 layer topology Michal Wilczynski
2022-07-20 14:40 ` [Intel-wired-lan] [PATCH net-next v6 2/4] ice: Adjust the VSI/Aggregator layers Michal Wilczynski
2022-07-20 14:40 ` [Intel-wired-lan] [PATCH net-next v6 3/4] ice: Enable switching default tx scheduler topology Michal Wilczynski
2022-07-20 14:40 ` [Intel-wired-lan] [PATCH net-next v6 4/4] ice: Add txbalancing devlink param Michal Wilczynski
2022-07-20 17:17 ` kernel test robot
2022-07-20 23:17 ` Tony Nguyen
2022-07-21 14:46 ` Wilczynski, Michal [this message]
2022-07-21 1:13 ` kernel test robot
2022-07-20 23:17 ` [Intel-wired-lan] [PATCH net-next v6 0/4] ice: Support 5 layer tx scheduler topology Tony Nguyen
2022-07-21 12:03 ` Wilczynski, Michal
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=97f5dd9e-b2f4-2a22-2ef7-9daabb70cb05@intel.com \
--to=michal.wilczynski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
/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