From: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
To: linux-rt-users@vger.kernel.org
Subject: Re: A question about the PREEMPT_RT patch set
Date: Tue, 9 Nov 2021 07:10:42 +0100 [thread overview]
Message-ID: <20211109071042.35f5da06@archlinux> (raw)
In-Reply-To: <80B78A8B8FEE6145A87579E8435D78C3023AB9B631@FZEX6.ruijie.com.cn>
On Tue, 9 Nov 2021 02:27:37 +0000:
>I have a question. If I apply the PREEMPT_RT patch set to the Linux
>kernel, is the real-time supported by the kernel hard real-time or
>soft real-time?
Hi,
when I programmed my C64 in Assembly I got no audible MIDI jitter,
using software written by other, the same was true for my Atari ST, on
my Linux PCs there very often is audible MIDI jitter and the amount of
jitter varies depending on the used MIDI interface. USB MIDI devices
are less accurate than PCI/PCIe devices.
What I try to point out is, that a lot of layers are involved, when
using a PC and apart from those layers some things are even not
real-time processed at all.
If you are using the PC to process audio signals (instead of MIDI)
there at least will be a minimal amount of a delay (latency) already
produced by the audio device's hardware.
In short, I don't know what it is called done by a rt patched Linux
kernel, but the result, including the communication with interfaces,
when using a PC, in my opinion doesn't fit the definition of "hard
real-time. OTOH some users have got success to use patched kernels for
CNC, but I don't know what patch is used.
To my understanding "hard real-time" is a squishy term when using a
multi-tasking, multi-user PC. Such machines are probably more suitable
as remote control for independent hard-realtime machines equipped with
microcontrollers.
Regards,
Ralf
prev parent reply other threads:[~2021-11-09 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 2:27 A question about the PREEMPT_RT patch set 余华兵(研发部 福州)
2021-11-09 6:10 ` Ralf Mardorf [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=20211109071042.35f5da06@archlinux \
--to=ralf.mardorf@alice-dsl.net \
--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