Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 8 Feb 2002 10:44:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 8 Feb 2002 10:44:33 -0500 Received: from garrincha.netbank.com.br ([200.203.199.88]:18958 "HELO netbank.com.br") by vger.kernel.org with SMTP id ; Fri, 8 Feb 2002 10:44:15 -0500 Date: Fri, 8 Feb 2002 13:43:44 -0200 (BRST) From: Rik van Riel X-X-Sender: To: Tigran Aivazian Cc: , Hugh Dickins Subject: Re: [patch] larger kernel stack (8k->16k) per task In-Reply-To: Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 8 Feb 2002, Tigran Aivazian wrote: > It also has a nice extra (/proc/stack) implemented by Hugh Dickins > which helps to find major offenders. That's really nice because it gives us the opportunity to look at the major offenders and see if we can fix those, instead of bloating up the kernel further. > Oh btw, please don't tell me "but now you'd need _four_ > physically-contiguous pages to create a task instead of two!" because > I know it (and think it's not too bad). On large machines ZONE_NORMAL is in a big squeeze, so growing a kernel data structure without any justification is a big no-no. I take it you've used /proc/stack to find out what the major offenders are ? If so, could you share the list of major offenders with us so we have an idea which functions to fix ? (I take it you must have run into some problems, otherwise you wouldn't have posted the patch) regards, Rik -- "Linux holds advantages over the single-vendor commercial OS" -- Microsoft's "Competing with Linux" document http://www.surriel.com/ http://distro.conectiva.com/ - 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/