From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263601AbUJ2V5t (ORCPT ); Fri, 29 Oct 2004 17:57:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263610AbUJ2Vy3 (ORCPT ); Fri, 29 Oct 2004 17:54:29 -0400 Received: from mailout.stusta.mhn.de ([141.84.69.5]:28938 "HELO mailout.stusta.mhn.de") by vger.kernel.org with SMTP id S263595AbUJ2VsB (ORCPT ); Fri, 29 Oct 2004 17:48:01 -0400 Date: Fri, 29 Oct 2004 23:47:23 +0200 From: Adrian Bunk To: torvalds@osdl.org, Andrew Morton Cc: linux-kernel@vger.kernel.org, Chris Wright Subject: [PATCH] uninline __sigqueue_alloc (fwd) Message-ID: <20041029214723.GX6677@stusta.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org The patch forwarded below still applies against 2.6.10-rc1-mm2. Was there any specific reason why it wasn't applied? ----- Forwarded message from Chris Wright ----- Date: Fri, 22 Oct 2004 14:35:51 -0700 From: Chris Wright To: torvalds@osdl.org Cc: linux-kernel@vger.kernel.org Subject: [PATCH] uninline __sigqueue_alloc Christoph suggests letting the compiler choose. No real compelling reason to inline anyhow. I had some vmlinux size numbers suggesting inline was better, but re-running them on newer kernel is giving different results, favoring uninline. Best let compiler choose. Un-inline __sigqueue_alloc. Signed-off-by: Chris Wright ===== kernel/signal.c 1.140 vs edited ===== --- 1.140/kernel/signal.c 2004-10-21 13:46:54 -07:00 +++ edited/kernel/signal.c 2004-10-22 14:00:00 -07:00 @@ -265,7 +265,7 @@ return sig; } -static inline struct sigqueue *__sigqueue_alloc(struct task_struct *t, int flags) +static struct sigqueue *__sigqueue_alloc(struct task_struct *t, int flags) { struct sigqueue *q = NULL; - 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/ ----- End forwarded message -----