Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752530AbdGMOx2 (ORCPT ); Thu, 13 Jul 2017 10:53:28 -0400 Received: from merlin.infradead.org ([205.233.59.134]:46926 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751915AbdGMOx1 (ORCPT ); Thu, 13 Jul 2017 10:53:27 -0400 Date: Thu, 13 Jul 2017 16:53:11 +0200 From: Peter Zijlstra To: "Li, Aubrey" Cc: Andi Kleen , Frederic Weisbecker , Christoph Lameter , Aubrey Li , tglx@linutronix.de, len.brown@intel.com, rjw@rjwysocki.net, tim.c.chen@linux.intel.com, arjan@linux.intel.com, paulmck@linux.vnet.ibm.com, yang.zhang.wz@gmail.com, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods Message-ID: <20170713145311.z4zxlyd2dospeoqg@hirez.programming.kicks-ass.net> References: <20170710172705.GA3441@tassilo.jf.intel.com> <20170711094157.5xcwkloxnjehieqv@hirez.programming.kicks-ass.net> <20170711160926.GA18805@lerouge> <20170711163422.etydkhhtgfthpfi5@hirez.programming.kicks-ass.net> <496d4921-5768-cd1e-654b-38630b7d2e13@linux.intel.com> <20170712083410.ualmvnvzoohyami5@hirez.programming.kicks-ass.net> <20170712213240.GE3441@tassilo.jf.intel.com> <20170713083649.febfflfl5hafkko5@hirez.programming.kicks-ass.net> <16e12e23-6b28-f174-7c4b-4d719225cd3b@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16e12e23-6b28-f174-7c4b-4d719225cd3b@linux.intel.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 821 Lines: 20 On Thu, Jul 13, 2017 at 10:48:55PM +0800, Li, Aubrey wrote: > - totally from arch_cpu_idle_enter entry to arch_cpu_idle_exit return costs > 9122ns - 15318ns. > ---- In this period(arch idle), rcu_idle_enter costs 1985ns - 2262ns, rcu_idle_exit > costs 1813ns - 3507ns > > Besides RCU, So Paul wants more details on where RCU hurts so we can try to fix. > the period includes c-state selection on X86, a few timestamp updates > and a few computations in menu governor. Also, deep HW-cstate latency can be up > to 100+ microseconds, even if the system is very busy, CPU still has chance to enter > deep cstate, which I guess some outburst workloads are not happy with it. > > That's my major concern without a fast idle path. Fixing C-state selection by creating an alternative idle path sounds so very wrong.