From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751560AbcGMUN2 (ORCPT ); Wed, 13 Jul 2016 16:13:28 -0400 Received: from mail-oi0-f42.google.com ([209.85.218.42]:36109 "EHLO mail-oi0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751247AbcGMUNU (ORCPT ); Wed, 13 Jul 2016 16:13:20 -0400 MIME-Version: 1.0 In-Reply-To: <20160713183347.GK4065@mtj.duckdns.org> References: <20160713182102.GJ4065@mtj.duckdns.org> <20160713183347.GK4065@mtj.duckdns.org> From: John Stultz Date: Wed, 13 Jul 2016 13:13:11 -0700 Message-ID: Subject: Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes To: Tejun Heo Cc: Ingo Molnar , Peter Zijlstra , lkml , Dmitry Shmidt , Rom Lemarchand , Colin Cross , Todd Kjos , Oleg Nesterov Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 13, 2016 at 11:33 AM, Tejun Heo wrote: > On Wed, Jul 13, 2016 at 02:21:02PM -0400, Tejun Heo wrote: >> One interesting thing to try would be replacing it with a regular >> non-percpu rwsem and see how it behaves. That should easily tell us >> whether this is from actual contention or artifacts from percpu_rwsem >> implementation. > > So, something like the following. Can you please see whether this > makes any difference? Yea. So this brings it down for me closer to what we're seeing with the Dmitry's patch reverting the two problematic commits, usually 10-50us with one early spike at 18ms. thanks -john