Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964848AbWEOKLu (ORCPT ); Mon, 15 May 2006 06:11:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932364AbWEOKLu (ORCPT ); Mon, 15 May 2006 06:11:50 -0400 Received: from mx04.stofanet.dk ([212.10.10.14]:56974 "EHLO mx04.stofanet.dk") by vger.kernel.org with ESMTP id S932348AbWEOKLt (ORCPT ); Mon, 15 May 2006 06:11:49 -0400 Date: Mon, 15 May 2006 12:10:20 +0200 From: Jens Axboe To: linux-kernel@vger.kernel.org Cc: mason@suse.com Subject: Re: [PATCH] fcache: a remapping boot cache Message-ID: <20060515101019.GA4068@suse.de> References: <20060515091806.GA4110@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060515091806.GA4110@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1119 Lines: 23 On Mon, May 15 2006, Jens Axboe wrote: > o Trying it on my notebook brought the time from the kernel starts > loading to kde has fully auto-logged in down from 50 seconds to 38 > seconds. The primed boot took 61 seconds. The notebook is about 4 > months old and the file system is very fresh, so better results should > be seen on more fragmented installs. Update - the above numbers were with an older version and with the cache partition located at the very end of the drive (hence being a lot slower than the root partition at the front). The fcache boot takes 33 seconds now, from the kernel starts loading to the kde login has finished. Probably 5 seconds of that time is device probe and network setup (dunno why the latter is still sleeping so much, I disabled dhcp for this test to avoid waits (for both fcache and normal boot, of course)). -- Jens Axboe - 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/