From: Chris Friesen <chris.friesen@windriver.com>
To: bpf@vger.kernel.org
Subject: status of BPF in conjunction with PREEMPT_RT for the 6.6 kernel?
Date: Thu, 9 Jan 2025 16:21:50 -0600 [thread overview]
Message-ID: <48d18ecf-41eb-4025-9bec-1dc606f343c3@windriver.com> (raw)
Hi,
Back in 2019 there were some concerns raised
(https://lwn.net/ml/bpf/20191017090500.ienqyium2phkxpdo@linutronix.de/#t)
around using BPF in conjunction with PREEMPT_RT.
In the context of the 6.6 kernel and the corresponding PREEMPT_RT
patchset, are those concerns still valid or have they been sorted out?
Please CC me on replies, I'm not subscribed to the list.
Thanks,
Chris Friesen
next reply other threads:[~2025-01-09 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 22:21 Chris Friesen [this message]
2025-01-10 2:06 ` status of BPF in conjunction with PREEMPT_RT for the 6.6 kernel? Hou Tao
[not found] ` <94a4475f-51a8-4113-b16f-c2239eb01537@windriver.com>
2025-01-11 4:07 ` Hou Tao
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=48d18ecf-41eb-4025-9bec-1dc606f343c3@windriver.com \
--to=chris.friesen@windriver.com \
--cc=bpf@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