From: David Miller <davem@davemloft.net>
To: tglx@linutronix.de
Cc: bigeasy@linutronix.de, daniel@iogearbox.net, bpf@vger.kernel.org,
ast@kernel.org, kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
peterz@infradead.org, williams@redhat.com
Subject: Re: [PATCH] BPF: Disable on PREEMPT_RT
Date: Thu, 17 Oct 2019 15:13:35 -0700 (PDT) [thread overview]
Message-ID: <20191017.151335.597242104804050107.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1910172342090.1869@nanos.tec.linutronix.de>
From: Thomas Gleixner <tglx@linutronix.de>
Date: Thu, 17 Oct 2019 23:54:07 +0200 (CEST)
> Clark might have some insight from the product side for you how much that
> impacts usability.
You won't even be able to load systemd, it uses bpf.
We're moving to the point where even LSM modules will be implemented in bpf.
IR drivers require bpf:
https://lwn.net/Articles/759188/
I understand the problems, and realize they are non-trivial, but this hammer
is really destructive on a fundamental level.
To a certain extent, those who insert bpf programs are explicitly
changing the kernel so really the onus is on them to make sure the
programs complete in time which is not only finite (which is
guaranteed by BPF) but also within the RT constraints.
next prev parent reply other threads:[~2019-10-17 22:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:05 [PATCH] BPF: Disable on PREEMPT_RT Sebastian Andrzej Siewior
2019-10-17 14:53 ` Daniel Borkmann
2019-10-17 15:40 ` Sebastian Andrzej Siewior
2019-10-17 17:25 ` David Miller
2019-10-17 21:54 ` Thomas Gleixner
2019-10-17 22:13 ` David Miller [this message]
2019-10-17 23:50 ` Thomas Gleixner
2019-10-17 23:27 ` Alexei Starovoitov
2019-10-18 0:22 ` Thomas Gleixner
2019-10-18 5:52 ` Alexei Starovoitov
2019-10-18 11:28 ` Thomas Gleixner
2019-10-18 12:48 ` Sebastian Sewior
2019-10-18 23:05 ` Alexei Starovoitov
2019-10-20 9:06 ` Thomas Gleixner
2019-10-22 1:43 ` Alexei Starovoitov
2019-10-18 2:49 ` Clark Williams
2019-10-18 4:57 ` David Miller
2019-10-18 5:54 ` Alexei Starovoitov
2019-10-18 8:38 ` Thomas Gleixner
2019-10-18 12:49 ` Clark Williams
2019-10-18 8:46 ` Thomas Gleixner
2019-10-18 12:43 ` Sebastian Sewior
2019-10-18 12:58 ` Clark Williams
2019-10-17 22:11 ` Thomas Gleixner
2019-10-17 22:23 ` David Miller
2019-10-17 17:26 ` David Miller
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=20191017.151335.597242104804050107.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
--cc=yhs@fb.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