From: Jakub Kicinski <kuba@kernel.org>
To: Suman Ghosh <sumang@marvell.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<sgoutham@marvell.com>, <sbhatta@marvell.com>,
<gakula@marvell.com>, <Sunil.Goutham@cavium.com>,
<hkelam@marvell.com>, <colin.king@intel.com>,
<netdev@vger.kernel.org>
Subject: Re: [net-next PATCH V2] octeontx2-pf: Add support for adaptive interrupt coalescing
Date: Mon, 16 May 2022 11:28:17 -0700 [thread overview]
Message-ID: <20220516112817.4f7d99cf@kernel.org> (raw)
In-Reply-To: <20220516105359.746919-1-sumang@marvell.com>
On Mon, 16 May 2022 16:23:59 +0530 Suman Ghosh wrote:
> @@ -1230,7 +1262,7 @@ static int otx2_set_link_ksettings(struct net_device *netdev,
>
> static const struct ethtool_ops otx2_ethtool_ops = {
> .supported_coalesce_params = ETHTOOL_COALESCE_USECS |
> - ETHTOOL_COALESCE_MAX_FRAMES,
> + ETHTOOL_COALESCE_MAX_FRAMES | ETHTOOL_COALESCE_USE_ADAPTIVE,
Ah there it is. Now you actually tested it with upstream :/
Please wrap the line.
Also please reject user trying to set asymmetric adaptive mode since
you don't seem to support it:
> + /* Check and update coalesce status */
> + if ((pfvf->flags & OTX2_FLAG_ADPTV_INT_COAL_ENABLED) ==
> + OTX2_FLAG_ADPTV_INT_COAL_ENABLED) {
> + priv_coalesce_status = 1;
> + if (!ec->use_adaptive_rx_coalesce || !ec->use_adaptive_tx_coalesce)
> + pfvf->flags &= ~OTX2_FLAG_ADPTV_INT_COAL_ENABLED;
> + } else {
> + priv_coalesce_status = 0;
> + if (ec->use_adaptive_rx_coalesce || ec->use_adaptive_tx_coalesce)
> + pfvf->flags |= OTX2_FLAG_ADPTV_INT_COAL_ENABLED;
If I'm reading this right user doing:
ethtool -C eth0 adaptive-rx on adaptive-tx off
multiple times will keep switching between adaptive and non-adaptive
mode. This will be super confusing to automation which may assume
configuration commands are idempotent.
next prev parent reply other threads:[~2022-05-16 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 10:53 [net-next PATCH V2] octeontx2-pf: Add support for adaptive interrupt coalescing Suman Ghosh
2022-05-16 18:28 ` Jakub Kicinski [this message]
2022-05-17 4:39 ` [EXT] " Suman Ghosh
-- strict thread matches above, loose matches on Subject: below --
2022-05-16 4:46 Suman Ghosh
2022-05-16 18:22 ` Jakub Kicinski
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=20220516112817.4f7d99cf@kernel.org \
--to=kuba@kernel.org \
--cc=Sunil.Goutham@cavium.com \
--cc=colin.king@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sumang@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.