From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 7 Oct 2002 23:06:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 7 Oct 2002 23:06:19 -0400 Received: from relay03.roc.frontiernet.net ([66.133.131.36]:42115 "EHLO relay03.roc.frontiernet.net") by vger.kernel.org with ESMTP id ; Mon, 7 Oct 2002 23:06:18 -0400 Date: Mon, 7 Oct 2002 23:12:04 -0400 From: Scott Mcdermott To: linux-kernel@vger.kernel.org Cc: Jan Hudec , Jesse Pollard , Oliver Neukum , Helge Hafting , "Martin J. Bligh" Subject: [OT] Re: The reason to call it 3.0 is the desktop (was Re: [OT] 2.6 not 3.0 - (NUMA)) Message-ID: <20021007231204.C3029@newbox.localdomain> References: <20021007141122.GA14423@vagabond> <200210071001.22467.pollard@admin.navo.hpc.mil> <20021007153438.GA14993@vagabond> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021007153438.GA14993@vagabond>; from bulb@ucw.cz on Mon, Oct 07, 2002 at 05:34:38PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Jan Hudec on Mon 7/10 17:34 +0200: > Well, depends on what we want to measure. If it's on the begining of > main, it measures library loading time. Then argument parsing, library > initialization, X initialization etc. can be measured. All those parts > should be timed so we can see where most time is spent and which can > be sped up. newer glibc prelinking support should help here a lot, according to publshed time trials I have seen with and without the feature.