Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757232AbYFTWr0 (ORCPT ); Fri, 20 Jun 2008 18:47:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754314AbYFTWrR (ORCPT ); Fri, 20 Jun 2008 18:47:17 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:45109 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1754191AbYFTWrQ (ORCPT ); Fri, 20 Jun 2008 18:47:16 -0400 Date: Fri, 20 Jun 2008 15:47:16 -0700 (PDT) Message-Id: <20080620.154716.75920403.davem@davemloft.net> To: mpatocka@redhat.com Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org, agk@redhat.com Subject: Re: stack overflow on Sparc64 From: David Miller In-Reply-To: References: <20080620.152847.169209890.davem@davemloft.net> X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 869 Lines: 23 From: Mikulas Patocka Date: Fri, 20 Jun 2008 18:36:09 -0400 (EDT) > On Fri, 20 Jun 2008, David Miller wrote: > > > Yes for debugging and other things it has to stay. > > If you want it to stay, then it doesn't make sense to make functions > tail-call-friendly --- because it should not crash with or without > debugging. On the contrary, of course it makes sense to do so. When debugging is disabled, the kernel will run faster. We have to fix the stack usage in either case, but from a performance standpoint when debugging is disabled the tail-call friendly layout is still highly desirable. -- 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/