public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@nabladev.com>
To: tobias.schaffner@siemens.com
Cc: cip-dev@lists.cip-project.org,
	nobuhiro.iwamatsu.x90@mail.toshiba,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Jan Altenberg <jan.altenberg@osadl.org>
Subject: Re: [cip-dev] preempt_rt on BeagleV-Fire
Date: Fri, 9 Jan 2026 10:58:58 +0100	[thread overview]
Message-ID: <aWDRYgwxThmOyGPr@duo.ucw.cz> (raw)
In-Reply-To: <36dd7fca-98e9-49ab-8dca-14a3997d0c5f@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]

Hi!

> has anyone already tested preempt_rt on the BeagleV-Fire?
> 
> OSADL has evaluated preempt_rt on both the PolarFire Icicle Kit
> (MPFS250T) and the PolarFire Discovery Kit (MPFS095T) and has reported
> rather problematic latency results so far[1].
> 
> Since the BeagleV-Fire is also based on a PolarFire SoC (MPFS025T), I
> suspect we might run into similar issues. Any experiences, measurements,
> or insights would be greatly appreciated.

Those OSADL results actually look good to me :-).

Ok, so let me explain. BeagleV-Fire seems to have slow CPUs. Like
"Nokia N900" slow. That's TI OMAP 3430 SoC, 600 MHz ARM Cortex-A8 CPU
from 2010 or so.

It is certainly less than 10% of speed of Core i9-9900K, and that one
reaches 100usec...

https://www.osadl.org/Latency-plot-of-system-in-rack-0-slot.qa-latencyplot-r0s5.0.html?latencies=&showno=&shadow=1&slider=360

...so 350usec is actually not that bad, AFAICT.

Not sure what our requirements are, sometimes people put the
time-critical stuff into FPGA.

Best regards,
								Pavel
-- 
In cooperation with Nabla.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2026-01-09  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08  8:53 preempt_rt on BeagleV-Fire Tobias Schaffner
2026-01-09  9:58 ` Pavel Machek [this message]
2026-01-09 11:08   ` [cip-dev] " Tobias Schaffner

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=aWDRYgwxThmOyGPr@duo.ucw.cz \
    --to=pavel@nabladev.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.altenberg@osadl.org \
    --cc=jan.kiszka@siemens.com \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    --cc=tobias.schaffner@siemens.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