From owner-freebsd-current@FreeBSD.ORG Mon Apr 21 05:12:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CE98106564A for ; Mon, 21 Apr 2008 05:12:33 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outJ.internet-mail-service.net (outj.internet-mail-service.net [216.240.47.233]) by mx1.freebsd.org (Postfix) with ESMTP id 5A0528FC2F for ; Mon, 21 Apr 2008 05:12:32 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Mon, 21 Apr 2008 12:02:20 -0700 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id CA5CB2D600E; Sun, 20 Apr 2008 22:12:31 -0700 (PDT) Message-ID: <480C223F.2040303@elischer.org> Date: Sun, 20 Apr 2008 22:12:31 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213) MIME-Version: 1.0 To: Daniel O'Connor References: <20080418003203.GB11705@dragon.NUXI.org> <48080276.3040203@elischer.org> <200804181235.29530.doconnor@gsoft.com.au> In-Reply-To: <200804181235.29530.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: gnn@freebsd.org, freebsd-current@freebsd.org, Andrew Gallatin Subject: Re: TSC Timecounter and multi-core/SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2008 05:12:33 -0000 Daniel O'Connor wrote: > On Fri, 18 Apr 2008, Julian Elischer wrote: >> David O'Brien wrote: >>> The TSC on K8 is not invariant - its rate of change is affected by >>> P-state changes. >>> >>> The TSC on Greyhound (Family 10h) is invariant. >>> [but as stated above, is not synced with other cores] >> You'd think that an invariant sync'd clock (fast to read) of some >> type would have been done by someone by now.. The software people >> have been asking for this for the last decade at least. > > Probably because it's very very difficult to get right :) and they've had over 20 years to think of something. >