From: Robert Hancock <robert.hancock@calian.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"claudiu.beznea@microchip.com" <claudiu.beznea@microchip.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
"tomas.melin@vaisala.com" <tomas.melin@vaisala.com>
Subject: Re: [PATCH net-next 0/2] MACB NAPI improvements
Date: Thu, 5 May 2022 17:56:51 +0000 [thread overview]
Message-ID: <4ae0701c105276b78e2bf6b69fad48a429cf4422.camel@calian.com> (raw)
In-Reply-To: <20220429223122.3642255-1-robert.hancock@calian.com>
On Fri, 2022-04-29 at 16:31 -0600, Robert Hancock wrote:
> Simplify the logic in the Cadence MACB/GEM driver for determining
> when to reschedule NAPI processing, and update it to use NAPI for the
> TX path as well as the RX path.
>
> Robert Hancock (2):
> net: macb: simplify/cleanup NAPI reschedule checking
> net: macb: use NAPI for TX completion path
>
> drivers/net/ethernet/cadence/macb.h | 1 +
> drivers/net/ethernet/cadence/macb_main.c | 193 ++++++++++++-----------
> 2 files changed, 106 insertions(+), 88 deletions(-)
>
Looks like this patchset is marked as Changes Requested in Patchwork, there was
some discussion but nothing that seemed like there was a conclusion that any
changes were needed. If anyone would like to see changes in another spin,
please let me know.
--
Robert Hancock
Senior Hardware Designer, Calian Advanced Technologies
www.calian.com
prev parent reply other threads:[~2022-05-05 17:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 22:31 [PATCH net-next 0/2] MACB NAPI improvements Robert Hancock
2022-04-29 22:31 ` [PATCH net-next 1/2] net: macb: simplify/cleanup NAPI reschedule checking Robert Hancock
2022-04-29 22:31 ` [PATCH net-next 2/2] net: macb: use NAPI for TX completion path Robert Hancock
2022-04-29 23:09 ` Robert Hancock
2022-05-03 7:22 ` Paolo Abeni
2022-05-03 18:34 ` Robert Hancock
2022-05-03 9:34 ` Tomas Melin
2022-05-03 17:01 ` Robert Hancock
2022-05-09 9:14 ` Harini Katakam
2022-05-09 19:46 ` Robert Hancock
2022-05-03 9:57 ` Tomas Melin
2022-05-03 17:07 ` Robert Hancock
2022-05-09 5:49 ` Tomas Melin
2022-05-09 18:00 ` Robert Hancock
2022-05-06 19:04 ` Robert Hancock
2022-05-05 17:56 ` Robert Hancock [this message]
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=4ae0701c105276b78e2bf6b69fad48a429cf4422.camel@calian.com \
--to=robert.hancock@calian.com \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=tomas.melin@vaisala.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).