Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755643Ab2JPSEb (ORCPT ); Tue, 16 Oct 2012 14:04:31 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:51438 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755372Ab2JPSE3 (ORCPT ); Tue, 16 Oct 2012 14:04:29 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 16 Oct 2012 21:04:28 +0300 X-Google-Sender-Auth: rwFW_2uY3GRJTk59wCo5sFz3x88 Message-ID: Subject: Re: Reading /proc/slabinfo causes stalls From: Pekka Enberg To: Avleen Vig Cc: linux-kernel@vger.kernel.org, Christoph Lameter , David Rientjes , Andrew Morton Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 891 Lines: 20 Hi Avleen, On Tue, Oct 16, 2012 at 8:51 PM, Avleen Vig wrote: > I *think* this is the right place to ask this, and apologies if it's not > (is there a better place?). > > We have checks which read /proc/slabinfo once a minute, and have noticed > that this causes the entire system to stall for a few milliseconds. > It's long enough that it causes noticeable delays in latency-sensitive > applications (between 10ms and 100ms). > > Is this a known condition? Are there work arounds or other ways to get the > slab allocation data which don't cause stalls? What kernel version are you using? What does your .config look like? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/