From owner-freebsd-hackers Mon Feb 18 12:41: 1 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D886F37B404; Mon, 18 Feb 2002 12:40:59 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1IKex936264; Mon, 18 Feb 2002 12:40:59 -0800 (PST) (envelope-from dillon) Date: Mon, 18 Feb 2002 12:40:59 -0800 (PST) From: Matthew Dillon Message-Id: <200202182040.g1IKex936264@apollo.backplane.com> To: Mike Smith Cc: John Polstra , hackers@FreeBSD.ORG Subject: ACPI timecounter tests original fast version vs masked version References: <20020204171736.A13719@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike, did you get my email clarifying what the masking code does? gettimeofday performance: 1 process / fast acpi timer 514000 calls/sec 1 process / dillon acpi timer 366284 calls/sec (previously posted patch set) 1 process / dillon acpi timer 395400 calls/sec with the mask <<= 2 instead of <<= 1 (one less bit of resolution) 2 processes with Giant completely removed from the path (userret and gettimeofday): 417000, 291000, and 316000. I don't have the performance for the original _slow code, sorry, but I believe it is similar to the the second and third sample due to it reading the timer three times at a minimum. In anycase, I think this is reasonable especially if we explicitly use the fast code for those chipsets known to be good. I would like to commit it. It can handle *ANY* sort of ripple or fast-carry breakage, really any type of breakage since it looks for two identical samples after masking rather then using an inequality. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message