Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753242AbYKZOjx (ORCPT ); Wed, 26 Nov 2008 09:39:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751506AbYKZOjn (ORCPT ); Wed, 26 Nov 2008 09:39:43 -0500 Received: from flusers.ccur.com ([12.192.68.2]:41448 "EHLO gamx.iccur.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751276AbYKZOjm (ORCPT ); Wed, 26 Nov 2008 09:39:42 -0500 Date: Wed, 26 Nov 2008 09:39:28 -0500 From: Joe Korty To: Alexey Dobriyan Cc: Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: [PATCH] Add per-cpu indexing to /proc/timer_list Message-ID: <20081126143928.GA16576@tsunami.ccur.com> Reply-To: Joe Korty References: <20081125224439.GA24042@tsunami.ccur.com> <20081125231445.GA24326@tsunami.ccur.com> <20081126045004.GA3278@x200.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081126045004.GA3278@x200.localdomain> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 951 Lines: 24 On Wed, Nov 26, 2008 at 07:50:04AM +0300, Alexey Dobriyan wrote: > On Tue, Nov 25, 2008 at 06:14:45PM -0500, Joe Korty wrote: > > Per-cpu indexing of /proc/timer_list. > > > > /proc/timer_list, potentially a very large file, is in > > danger of overflowing its seq_file buffer. So 'split up' > > the buffering on cpu ID boundaries. This should make this > > file more likely to be useful on largish SMP systems. > > What do you mean? > > You can't overflow seq_file buffer unless kmalloc() will fail large > allocation. And changing internals doesn't change amount of stuff > to be shown, which is the only thing which can lead to large buffer > need. You're right, I missed the re-malloc part. Joe -- 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/