From: "Marc Strämke" <marc.straemke@eltropuls.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: Latency spikes on V6.15.1 Preempt RT and maybe related to intel? IGB
Date: Tue, 17 Jun 2025 11:45:52 +0200 [thread overview]
Message-ID: <bb74b5b6-bc23-4aa4-83df-449dc7c9006b@eltropuls.de> (raw)
In-Reply-To: <20250617092814.vqKdu23w@linutronix.de>
Hi Sebastian,
On 17.06.25 11:28, Sebastian Andrzej Siewior wrote:
> Between those two functions you have 800us delay. Interrupts are not
> disabled so the CPU stalls. As explained earlier, I expect the read on
> the bus flushes the writes causing the spike.
>
So the delay you think is really the hardware(CPU) being stalled on the
bus for so long? Or do you mean that this is the reason for the long
runtime of the IGB function only?
Shouldn't the other core (it is 2 core machine) still be able to handle
the timer interrupt then? (I did some testing with isolating IP on one
core and cyclictest on the other, I am not sure if I moved the timer IRQ
to the second core)
My mistake was to search for where the Interrupt was being disabled in
Kernelspace (I did not think that the hardware could introduce and IRQ
delay for 800us..)
Marc
next prev parent reply other threads:[~2025-06-17 9:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 11:23 Latency spikes on V6.15.1 Preempt RT and maybe related to intel IGB Marc Strämke
2025-06-13 14:54 ` Sebastian Andrzej Siewior
[not found] ` <E1uQ6I0-000000003aa-37uJ@smtprelay05.ispgateway.de>
2025-06-13 19:58 ` Latency spikes on V6.15.1 Preempt RT and maybe related to intel? IGB Sebastian Andrzej Siewior
2025-06-14 8:52 ` Marc Strämke
2025-06-16 15:10 ` Marc Strämke
2025-06-17 9:16 ` Sebastian Andrzej Siewior
2025-06-17 9:08 ` Sebastian Andrzej Siewior
2025-06-17 9:28 ` Sebastian Andrzej Siewior
2025-06-17 9:45 ` Marc Strämke [this message]
2025-06-17 10:00 ` Sebastian Andrzej Siewior
2025-06-17 10:03 ` Marc Strämke
2025-06-17 10:15 ` Sebastian Andrzej Siewior
2025-06-17 10:54 ` Kurt Kanzenbach
[not found] ` <19a46896-3d26-415b-9820-730a42b0702e@eltropuls.de>
2025-06-17 13:35 ` Kurt Kanzenbach
[not found] ` <522704b0-5a35-42c3-9bcc-627b487b740c@eltropuls.de>
2025-06-14 18:13 ` Latency spikes on V6.15.1 Preempt RT and maybe related to intel IGB Sebastian Andrzej Siewior
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=bb74b5b6-bc23-4aa4-83df-449dc7c9006b@eltropuls.de \
--to=marc.straemke@eltropuls.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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®