Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268039AbUJVVoN (ORCPT ); Fri, 22 Oct 2004 17:44:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267921AbUJVVoI (ORCPT ); Fri, 22 Oct 2004 17:44:08 -0400 Received: from fw.osdl.org ([65.172.181.6]:29878 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S268040AbUJVVfy (ORCPT ); Fri, 22 Oct 2004 17:35:54 -0400 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 Message-ID: <20041022143551.Z2357@build.pdx.osdl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 971 Lines: 24 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/