From: Enguerrand de Ribaucourt <enguerrand.de-ribaucourt@savoirfairelinux.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: davem <davem@davemloft.net>, netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux <linux@armlinux.org.uk>, hkallweit1 <hkallweit1@gmail.com>
Subject: Re: [PATCH 1/2] net: dp83822: disable false carrier interrupt
Date: Thu, 23 Jun 2022 09:16:28 -0400 (EDT) [thread overview]
Message-ID: <1572348291.280163.1655990188458.JavaMail.zimbra@savoirfairelinux.com> (raw)
In-Reply-To: <YrRfzph6jyg2pUyO@lunn.ch>
----- Original Message -----
> From: "Andrew Lunn" <andrew@lunn.ch>
> To: "Enguerrand de Ribaucourt" <enguerrand.de-ribaucourt@savoirfairelinux.com>
> Cc: "davem" <davem@davemloft.net>, "netdev" <netdev@vger.kernel.org>, "linux-kernel" <linux-kernel@vger.kernel.org>,
> "linux" <linux@armlinux.org.uk>, "hkallweit1" <hkallweit1@gmail.com>
> Sent: Thursday, June 23, 2022 2:42:54 PM
> Subject: Re: [PATCH 1/2] net: dp83822: disable false carrier interrupt
> On Thu, Jun 23, 2022 at 10:51:25AM +0200, Enguerrand de Ribaucourt wrote:
> > When unplugging an Ethernet cable, false carrier events were produced by
> > the PHY at a very high rate. Once the false carrier counter full, an
> > interrupt was triggered every few clock cycles until the cable was
> > replugged. This resulted in approximately 10k/s interrupts.
> > Since the false carrier counter (FCSCR) is never used, we can safely
> > disable this interrupt.
> > In addition to improving performance, this also solved MDIO read
> > timeouts I was randomly encountering with an i.MX8 fec MAC because of
> > the interrupt flood. The interrupt count and MDIO timeout fix were
> > tested on a v5.4.110 kernel.
> Since this is version 2, you should add v2 into the subject line. See
> the submitting patches document in the kernel documentation.
> Also, with patch sets, please include a patch 0/X which describes the
> big picture.
> This is also a bug fix, you are stopping an interrupt storm. So please
> include a Fixes: tag indicating where the issue was introduced.
> The code itself looks good, it is just getting the processes right.
> Andrew
Sorry, I'm still not familiar with the process. I resubmitted the patches
with your recommendations.
Thank you very much for your advice.
Enguerrand
next prev parent reply other threads:[~2022-06-23 13:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 13:46 [PATCH] " Enguerrand de Ribaucourt
2022-06-17 17:55 ` Andrew Lunn
2022-06-23 8:51 ` Enguerrand de Ribaucourt
2022-06-23 8:51 ` [PATCH 1/2] " Enguerrand de Ribaucourt
2022-06-23 12:42 ` Andrew Lunn
2022-06-23 13:16 ` Enguerrand de Ribaucourt [this message]
2022-06-23 8:51 ` [PATCH 2/2] net: dp83822: disable rx error interrupt Enguerrand de Ribaucourt
2022-06-23 13:06 ` [PATCH v2 0/2] net: dp83822: fix interrupt floods Enguerrand de Ribaucourt
2022-06-23 13:06 ` [PATCH v2 1/2] net: dp83822: disable false carrier interrupt Enguerrand de Ribaucourt
2022-06-23 13:06 ` [PATCH v2 2/2] net: dp83822: disable rx error interrupt Enguerrand de Ribaucourt
2022-06-23 13:14 ` [PATCH v2 0/2] net: dp83822: fix interrupt floods Enguerrand de Ribaucourt
2022-06-23 13:14 ` [PATCH v2 1/2] net: dp83822: disable false carrier interrupt Enguerrand de Ribaucourt
2022-06-23 13:14 ` [PATCH v2 2/2] net: dp83822: disable rx error interrupt Enguerrand de Ribaucourt
2022-06-23 13:46 ` [PATCH v3 0/2] net: dp83822: fix interrupt floods Enguerrand de Ribaucourt
2022-06-23 13:46 ` [PATCH v3 1/2] net: dp83822: disable false carrier interrupt Enguerrand de Ribaucourt
2022-06-23 18:27 ` Andrew Lunn
2022-06-23 13:46 ` [PATCH v3 2/2] net: dp83822: disable rx error interrupt Enguerrand de Ribaucourt
2022-06-23 18:24 ` [PATCH v3 0/2] net: dp83822: fix interrupt floods Andrew Lunn
2022-06-24 23:50 ` 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=1572348291.280163.1655990188458.JavaMail.zimbra@savoirfairelinux.com \
--to=enguerrand.de-ribaucourt@savoirfairelinux.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®