Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1343045

Re: [PATCH tip/core/rcu 03/13] rcu: Stop treating in-kernel CPU-bound workloads as errors

From Peter Zijlstra <peterz@infradead.org>
Newsgroups linux.kernel
Subject Re: [PATCH tip/core/rcu 03/13] rcu: Stop treating in-kernel CPU-bound workloads as errors
Date 2016-02-25 10:50 +0100
Message-ID <r60IA-1NY-47@gated-at.bofh.it> (permalink)
References <r5A1H-87D-5@gated-at.bofh.it> <r5A1I-87D-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue, Feb 23, 2016 at 09:12:40PM -0800, Paul E. McKenney wrote:
> Commit 4a81e8328d379 ("Reduce overhead of cond_resched() checks for RCU")
> handles the error case where a nohz_full loops indefinitely in the kernel
> with the scheduling-clock interrupt disabled.  However, this handling
> includes IPIing the CPU running the offending loop, which is not what
> we want for real-time workloads.  And there are starting to be real-time
> CPU-bound in-kernel workloads, and these must be handled without IPIing
> the CPU, at least not in the common case.  Therefore, this situation can
> no longer be dismissed as an error case.

Do explain. Doing "for (;;) ;" in a kernel RT thread is just as bad for
general system health as is doing the same in userspace.

Also, who runs his RT workload in-kernel ?

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH tip/core/rcu 03/13] rcu: Stop treating in-kernel CPU-bound workloads as errors "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-02-24 06:20 +0100
  Re: [PATCH tip/core/rcu 03/13] rcu: Stop treating in-kernel  CPU-bound workloads as errors Peter Zijlstra <peterz@infradead.org> - 2016-02-25 10:50 +0100
    Re: [PATCH tip/core/rcu 03/13] rcu: Stop treating in-kernel  CPU-bound workloads as errors "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-02-25 18:30 +0100

csiph-web