From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934376AbXG0NgR (ORCPT ); Fri, 27 Jul 2007 09:36:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760367AbXG0NgE (ORCPT ); Fri, 27 Jul 2007 09:36:04 -0400 Received: from sandeen.net ([209.173.210.139]:10950 "EHLO sandeen.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758209AbXG0NgA (ORCPT ); Fri, 27 Jul 2007 09:36:00 -0400 X-Greylist: delayed 2024 seconds by postgrey-1.27 at vger.kernel.org; Fri, 27 Jul 2007 09:36:00 EDT Message-ID: <46A9ED28.3070508@sandeen.net> Date: Fri, 27 Jul 2007 08:03:36 -0500 From: Eric Sandeen User-Agent: Thunderbird 2.0.0.5 (Macintosh/20070716) MIME-Version: 1.0 To: Alan Cox CC: Andrea Arcangeli , Matt Mackall , Rene Herman , Ray Lee , Bodo Eggert <7eggert@gmx.de>, Jeremy Fitzhardinge , Jesper Juhl , Linux Kernel Mailing List , William Lee Irwin III , David Chinner , Arjan van de Ven Subject: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...? References: <8GVjY-PL-25@gated-at.bofh.it> <469A5D7C.5010904@gmail.com> <469BF104.1040703@gmail.com> <2c0942db0707161537o2852a308s26e79235e897e282@mail.gmail.com> <469BF768.6040200@gmail.com> <20070716230719.GC11115@waste.org> <469BFB73.3070105@gmail.com> <20070716232755.GD11115@waste.org> <20070719001539.GC29728@v2.random> <20070719013955.1bedc423@the-village.bc.nu> In-Reply-To: <20070719013955.1bedc423@the-village.bc.nu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Alan Cox wrote: >> About 4k stacks I was generally against them, much better to fail in >> fork than to risk corruption. The per-irq stack part is great feature >> instead (too bad it wasn't enabled for the safer 8k stacks). > > 8K stacks without IRQ stacks are not "safer" so I don't understand your > comment ? Hmm was it SuSE or RH kernels (or mainline?) I saw which had a test to defer soft IRQs if they occurred too deep in the stack for the current thread. -Eric