From: Jakub Kicinski <kuba@kernel.org>
To: Suman Ghosh <sumang@marvell.com>
Cc: <pabeni@redhat.com>, <davem@davemloft.net>,
<sgoutham@marvell.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH V3] octeontx2-pf: Add support for adaptive interrupt coalescing
Date: Mon, 9 May 2022 17:42:34 -0700 [thread overview]
Message-ID: <20220509174234.4a31ff92@kernel.org> (raw)
In-Reply-To: <20220509174145.629b04df@kernel.org>
On Mon, 9 May 2022 17:41:45 -0700 Jakub Kicinski wrote:
> On Fri, 6 May 2022 11:15:19 +0530 Suman Ghosh wrote:
> > Added support for adaptive IRQ coalescing. It uses net_dim
> > algorithm to find the suitable delay/IRQ count based on the
> > current packet rate.
> >
> > Signed-off-by: Suman Ghosh <sumang@marvell.com>
> > Reviewed-by: Sunil Kovvuri Goutham <sgoutham@marvell.com>
>
> Have you tested this?
It doesn't apply to net-next.
next prev parent reply other threads:[~2022-05-10 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 5:45 [PATCH V3] octeontx2-pf: Add support for adaptive interrupt coalescing Suman Ghosh
2022-05-10 0:41 ` Jakub Kicinski
2022-05-10 0:42 ` Jakub Kicinski [this message]
2022-05-10 4:18 ` [EXT] " Suman Ghosh
2022-05-10 20:03 ` 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=20220509174234.4a31ff92@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).