From: Wojciech Drewek <wojciech.drewek@intel.com>
To: Suman Ghosh <sumang@marvell.com>, <sgoutham@marvell.com>,
<gakula@marvell.com>, <sbhatta@marvell.com>, <hkelam@marvell.com>,
<lcherian@marvell.com>, <jerinj@marvell.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <horms@kernel.org>,
<naveenm@marvell.com>
Subject: Re: [net PATCH v3] octeontx2-pf: consider both Rx and Tx packet stats for adaptive interrupt coalescing
Date: Fri, 1 Dec 2023 11:44:45 +0100 [thread overview]
Message-ID: <bb7d635a-8cea-4fcd-9d27-fb9e3d82cab9@intel.com> (raw)
In-Reply-To: <20231201053330.3903694-1-sumang@marvell.com>
On 01.12.2023 06:33, Suman Ghosh wrote:
> From: Naveen Mamindlapalli <naveenm@marvell.com>
>
> The current adaptive interrupt coalescing code updates only rx
> packet stats for dim algorithm. This patch also updates tx packet
> stats which will be useful when there is only tx traffic.
> Also moved configuring hardware adaptive interrupt setting to
> driver dim callback.
>
> Fixes: 6e144b47f560 ("octeontx2-pf: Add support for adaptive interrupt coalescing")
> Signed-off-by: Naveen Mamindlapalli <naveenm@marvell.com>
> Signed-off-by: Suman Ghosh <sumang@marvell.com>
> ---
Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
> v3 changes:
> - Updated signed-off-by signature.
>
> v2 changes:
> - Missed adding the fixes tag in v1. Added the same in v2.
>
> .../ethernet/marvell/octeontx2/nic/otx2_pf.c | 9 +++++++++
> .../marvell/octeontx2/nic/otx2_txrx.c | 20 +++++++++----------
> 2 files changed, 19 insertions(+), 10 deletions(-)
>
next prev parent reply other threads:[~2023-12-01 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 5:33 [net PATCH v3] octeontx2-pf: consider both Rx and Tx packet stats for adaptive interrupt coalescing Suman Ghosh
2023-12-01 10:44 ` Wojciech Drewek [this message]
2023-12-05 2:40 ` patchwork-bot+netdevbpf
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=bb7d635a-8cea-4fcd-9d27-fb9e3d82cab9@intel.com \
--to=wojciech.drewek@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox