From owner-cvs-all Tue Apr 2 21:12: 6 2002 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 085D037B419; Tue, 2 Apr 2002 21:12:00 -0800 (PST) Received: (from marcel@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g335C0u29225; Tue, 2 Apr 2002 21:12:00 -0800 (PST) (envelope-from marcel) Message-Id: <200204030512.g335C0u29225@freefall.freebsd.org> From: Marcel Moolenaar Date: Tue, 2 Apr 2002 21:11:59 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/ia64/ia64 ia64dump.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG marcel 2002/04/02 21:11:59 PST Modified files: sys/ia64/ia64 ia64dump.c Log: Use a twiddle to show that we're busy dumping. The initial code emitted the total number of pages it still had to dump prior to dumping a block of up to 16 pages. For a 128MB region this would result in 8M number of printf()s. Barf! The problem in general is that memory typically has one really big region and a number of "scattered" smaller regions. Some may even be just a few pages. The twiddle works best for now, but it doesn't really give a good progress indication for the large regions. Those are the cases where you definitely want good PI to avoid having the user turn into a twiddle :-) Revision Changes Path 1.2 +7 -5 src/sys/ia64/ia64/ia64dump.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message