Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 28 Jul 2002 17:25:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 28 Jul 2002 17:25:01 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:18447 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id ; Sun, 28 Jul 2002 17:25:00 -0400 Message-ID: <3D4463F1.F6981B0@zip.com.au> Date: Sun, 28 Jul 2002 14:36:49 -0700 From: Andrew Morton X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.19-rc3-ac3 i686) X-Accept-Language: en MIME-Version: 1.0 To: Ingo Molnar CC: lkml Subject: Re: inlines in kernel/sched.c References: <3D445F53.BDE6B754@zip.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 984 Lines: 33 Ingo Molnar wrote: > > On Sun, 28 Jul 2002, Andrew Morton wrote: > > > Ingo, could you please review the use of inlines in the > > scheduler sometime? They seem to be excessive. > > > > For example, this patch reduces the sched.d icache footprint > > by 1.5 kilobytes. > > the patch also hurts context-switch latencies - it went > from 1.35 usecs to 1.42 usecs - a 5% drop. > It will hurt with benchmarks, because with benchmarks all of the scheuler is in L1 all the time. This stuff's hard. I don't know what the right answer is, really. To optimise for scheduler-intensive workloads we should optimise for the all-in-cache case. To optimise for other workloads we should aim to reduce the cache footprint. Perhaps. Dunno. - - 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/