Re: [PATCH 03/11 v3] ftrace: Optimize testing what context current is in

2020-11-09 Thread Steven Rostedt
On Mon, 9 Nov 2020 13:17:08 +0100 Peter Zijlstra wrote: > This patch is misleading, it doesn't optimize it nearly as much as is > possible and actually fixes the softirq case, which isn't at all > mentioned. This is actually an old patch I had for some time (it's been in the ring buffer code for

Re: [PATCH 03/11 v3] ftrace: Optimize testing what context current is in

2020-11-09 Thread Peter Zijlstra
On Thu, Nov 05, 2020 at 09:32:38PM -0500, Steven Rostedt wrote: > From: "Steven Rostedt (VMware)" > > The preempt_count() is not a simple location in memory, it could be part of > per_cpu code or more. Each access to preempt_count(), or one of its accessor > functions (like in_interrupt()) takes

[PATCH 03/11 v3] ftrace: Optimize testing what context current is in

2020-11-05 Thread VMware
From: "Steven Rostedt (VMware)" The preempt_count() is not a simple location in memory, it could be part of per_cpu code or more. Each access to preempt_count(), or one of its accessor functions (like in_interrupt()) takes several cycles. By reading preempt_count() once, and then doing tests to f