BPF List
 help / color / mirror / Atom feed
From: Hou Tao <houtao1@huawei.com>
To: Chris Friesen <chris.friesen@windriver.com>,
	<bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: status of BPF in conjunction with PREEMPT_RT for the 6.6 kernel?
Date: Fri, 10 Jan 2025 10:06:36 +0800	[thread overview]
Message-ID: <d39cfb84-7b0e-e73b-f2ba-bee32e883a48@huawei.com> (raw)
In-Reply-To: <48d18ecf-41eb-4025-9bec-1dc606f343c3@windriver.com>

Hi,

On 1/10/2025 6:21 AM, Chris Friesen wrote:
> 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.

Do you have any use case for BPF + PREEMPT_RT ?  I am not a RT expert,
however, In my understanding, BPF + PREEMPT_RT in the vanilla kernel
basically can work togerther basically. The memory allocation concern is
partially resolved and there is still undergoing effort trying to
resolve it [1]. The up_read_non_owner problem has been avoided
explicitly and the non-preemptible context for bpf prog has also been
fixed. Although the running of test_maps and test_progs under PREEMPT_RT
report some problems, I think these problem could be fixed. As for v6.6,
I think it may be OK for BPF + PREEMPT_RT case.

[1]:
https://lore.kernel.org/bpf/20241210023936.46871-1-alexei.starovoitov@gmail.com/
> Thanks,
> Chris Friesen
>
>
> .


  reply	other threads:[~2025-01-10  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 22:21 status of BPF in conjunction with PREEMPT_RT for the 6.6 kernel? Chris Friesen
2025-01-10  2:06 ` Hou Tao [this message]
     [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=d39cfb84-7b0e-e73b-f2ba-bee32e883a48@huawei.com \
    --to=houtao1@huawei.com \
    --cc=ast@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=bpf@vger.kernel.org \
    --cc=chris.friesen@windriver.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