Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932711AbVLSJjY (ORCPT ); Mon, 19 Dec 2005 04:39:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932713AbVLSJjX (ORCPT ); Mon, 19 Dec 2005 04:39:23 -0500 Received: from embla.aitel.hist.no ([158.38.50.22]:61856 "HELO embla.aitel.hist.no") by vger.kernel.org with SMTP id S932711AbVLSJjX (ORCPT ); Mon, 19 Dec 2005 04:39:23 -0500 Message-ID: <43A680B1.50502@aitel.hist.no> Date: Mon, 19 Dec 2005 10:43:13 +0100 From: Helge Hafting User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stefan Rompf CC: Arjan van de Ven , linux-kernel@vger.kernel.org Subject: Re: [2.6 patch] i386: always use 4k/4k stacks References: <200512181149.02009.stefan@loplof.de> <1134904884.9626.7.camel@laptopd505.fenrus.org> <200512181304.38054.stefan@loplof.de> In-Reply-To: <200512181304.38054.stefan@loplof.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 637 Lines: 17 Stefan Rompf wrote: >Wrong. The probability that an interrupt happens just during the codepath with >highest stack usage is very small. Anyway CONFIG_DEBUG_STACKOVERFLOW is not >enabled in 2.6.14.4 i386 defconfig. Don't know about vendor kernel kernels >though. > > Well, the interrupts have their own stack (if using 4k stacks) so the interrupt timing shouldn't matter. Helge Hafting - 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/