From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: sasha.neftin@intel.com,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
richardcochran@gmail.com, kurt@linutronix.de,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com
Subject: [Intel-wired-lan] [iwl-net v1 0/2] igc/igb: Fix missing time sync events
Date: Fri, 16 Feb 2024 17:04:52 -0800 [thread overview]
Message-ID: <20240217010455.58258-1-vinicius.gomes@intel.com> (raw)
Hi,
It was reported that i225/i226 could sometimes miss some time sync
events when two or more types of events (PPS and Timestamps was used
by the reporter) are being used at the same time under heavy traffic.
The core issue is that the driver was double clearing interrupts, as
the register is both "read to clear" and "write 1 to clear"
(documented in section 8.16.1 of the datasheet), and the handler was
doing both. Which could cause events to be missed if they happen
between the "read" and the "write".
Removing the write fixes the issue.
It was tracked down to commit 2c344ae24501 ("igc: Add support for TX
timestamping"), in which I added support for basic timestamp
operations, the issue is that as the hardware operates very similarly
to i210, I used igb code as inspiration. And indeed, the same double
clearing is present there.
But in the igb case, I haven't seen myself or heard about any issues
that seem related to this. So I think it's more like a possible issue.
But it seems like a good idea to fix it there was well.
Vinicius Costa Gomes (2):
igc: Fix missing time sync events
igb: Fix missing time sync events
drivers/net/ethernet/intel/igb/igb_main.c | 23 +++++------------------
drivers/net/ethernet/intel/igc/igc_main.c | 12 +-----------
2 files changed, 6 insertions(+), 29 deletions(-)
--
2.43.2
next reply other threads:[~2024-02-17 1:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 1:04 Vinicius Costa Gomes [this message]
2024-02-17 1:04 ` [Intel-wired-lan] [iwl-net v1 1/2] igc: Fix missing time sync events Vinicius Costa Gomes
2024-02-18 15:40 ` Kurt Kanzenbach
2024-02-17 1:04 ` [Intel-wired-lan] [iwl-net v1 2/2] igb: " Vinicius Costa Gomes
2024-02-17 15:05 ` Richard Cochran
2024-02-17 16:55 ` Richard Cochran
2024-02-20 17:30 ` Vinicius Costa Gomes
2024-02-17 15:13 ` [Intel-wired-lan] [iwl-net v1 0/2] igc/igb: " Richard Cochran
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=20240217010455.58258-1-vinicius.gomes@intel.com \
--to=vinicius.gomes@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kurt@linutronix.de \
--cc=richardcochran@gmail.com \
--cc=sasha.neftin@intel.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