From: Simon Horman <horms@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel.com>,
sasha.neftin@intel.com, Naama Meir <naamax.meir@linux.intel.com>
Subject: Re: [PATCH net 2/2] igc: Modify the tx-usecs coalesce setting
Date: Sun, 30 Jul 2023 17:54:09 +0200 [thread overview]
Message-ID: <ZMaHobBXLeJS0dsj@kernel.org> (raw)
In-Reply-To: <20230728170954.2445592-3-anthony.l.nguyen@intel.com>
On Fri, Jul 28, 2023 at 10:09:54AM -0700, Tony Nguyen wrote:
> From: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel.com>
>
> This patch enables users to modify the tx-usecs parameter.
> The rx-usecs value will adhere to the same value as tx-usecs
> if the queue pair setting is enabled.
>
> How to test:
> User can set the coalesce value using ethtool command.
>
> Example command:
> Set: ethtool -C <interface>
>
> Previous output:
>
> root@P12DYHUSAINI:~# ethtool -C enp170s0 tx-usecs 10
> netlink error: Invalid argument
>
> New output:
>
> root@P12DYHUSAINI:~# ethtool -C enp170s0 tx-usecs 10
> rx-usecs: 10
> rx-frames: n/a
> rx-usecs-irq: n/a
> rx-frames-irq: n/a
>
> tx-usecs: 10
> tx-frames: n/a
> tx-usecs-irq: n/a
> tx-frames-irq: n/a
>
> Fixes: 8c5ad0dae93c ("igc: Add ethtool support")
> Signed-off-by: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel.com>
> Tested-by: Naama Meir <naamax.meir@linux.intel.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> ---
> drivers/net/ethernet/intel/igc/igc_ethtool.c | 33 ++++++++++++++++++--
> 1 file changed, 30 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/igc/igc_ethtool.c b/drivers/net/ethernet/intel/igc/igc_ethtool.c
> index 62d925b26f2c..1cf7131a82c5 100644
> --- a/drivers/net/ethernet/intel/igc/igc_ethtool.c
> +++ b/drivers/net/ethernet/intel/igc/igc_ethtool.c
> @@ -914,6 +914,34 @@ static int igc_ethtool_set_coalesce(struct net_device *netdev,
> adapter->flags &= ~IGC_FLAG_DMAC;
> }
>
> + if (adapter->flags & IGC_FLAG_QUEUE_PAIRS) {
> + u32 old_tx_itr, old_rx_itr;
> +
> + /* This is to get back the original value before byte shifting */
> + old_tx_itr = (adapter->tx_itr_setting <= 3) ?
> + adapter->tx_itr_setting : adapter->tx_itr_setting >> 2;
> +
> + old_rx_itr = (adapter->rx_itr_setting <= 3) ?
> + adapter->rx_itr_setting : adapter->rx_itr_setting >> 2;
> +
> + if (old_tx_itr != ec->tx_coalesce_usecs) {
> + if (ec->tx_coalesce_usecs && ec->tx_coalesce_usecs <= 3)
> + adapter->tx_itr_setting = ec->tx_coalesce_usecs;
> + else
> + adapter->tx_itr_setting = ec->tx_coalesce_usecs << 2;
> +
> + adapter->rx_itr_setting = adapter->tx_itr_setting;
> + } else if (old_rx_itr != ec->rx_coalesce_usecs) {
> + if (ec->rx_coalesce_usecs && ec->rx_coalesce_usecs <= 3)
> + adapter->rx_itr_setting = ec->rx_coalesce_usecs;
> + else
> + adapter->rx_itr_setting = ec->rx_coalesce_usecs << 2;
> +
> + adapter->tx_itr_setting = adapter->rx_itr_setting;
> + }
> + goto program_itr;
This goto seems fairly gratuitous to me.
Couldn't the code be refactored to avoid it,
f.e. by moving ~10 lines below into an else clause?
My main objection here is readability,
I have no objections about correctness.
> + }
> +
> /* convert to rate of irq's per second */
> if (ec->rx_coalesce_usecs && ec->rx_coalesce_usecs <= 3)
> adapter->rx_itr_setting = ec->rx_coalesce_usecs;
> @@ -921,13 +949,12 @@ static int igc_ethtool_set_coalesce(struct net_device *netdev,
> adapter->rx_itr_setting = ec->rx_coalesce_usecs << 2;
>
> /* convert to rate of irq's per second */
> - if (adapter->flags & IGC_FLAG_QUEUE_PAIRS)
> - adapter->tx_itr_setting = adapter->rx_itr_setting;
> - else if (ec->tx_coalesce_usecs && ec->tx_coalesce_usecs <= 3)
> + if (ec->tx_coalesce_usecs && ec->tx_coalesce_usecs <= 3)
> adapter->tx_itr_setting = ec->tx_coalesce_usecs;
> else
> adapter->tx_itr_setting = ec->tx_coalesce_usecs << 2;
>
> +program_itr:
> for (i = 0; i < adapter->num_q_vectors; i++) {
> struct igc_q_vector *q_vector = adapter->q_vector[i];
>
> --
> 2.38.1
>
>
next prev parent reply other threads:[~2023-07-30 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 17:09 [PATCH net 0/2][pull request] igc: Enhance the tx-usecs coalesce setting implementation Tony Nguyen
2023-07-28 17:09 ` [PATCH net 1/2] igc: Expose tx-usecs coalesce setting to user Tony Nguyen
2023-07-28 17:09 ` [PATCH net 2/2] igc: Modify the tx-usecs coalesce setting Tony Nguyen
2023-07-30 15:54 ` Simon Horman [this message]
2023-07-31 3:53 ` Zulkifli, Muhammad Husaini
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=ZMaHobBXLeJS0dsj@kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=muhammad.husaini.zulkifli@intel.com \
--cc=naamax.meir@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sasha.neftin@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).