From owner-freebsd-current@FreeBSD.ORG Fri Oct 28 13:39:24 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 21E1616A41F; Fri, 28 Oct 2005 13:39:20 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <436229CF.6040001@freebsd.org> Date: Fri, 28 Oct 2005 21:38:23 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <32412.1130505646@critter.freebsd.dk> In-Reply-To: <32412.1130505646@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Pertti Kosunen , Robert Watson , current@freebsd.org, "Yuriy N. Shkandybin" Subject: Re: Timers and timing, was: MySQL Performance 6.0rc1 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: Fri, 28 Oct 2005 13:39:24 -0000 Poul-Henning Kamp wrote: >>On the other hand, a lower risk change might be to simply add a new CLOCK_ >>type for lower resolution, and have a timer synchronize a variable to the >>system clock once every 1/10 of a second. This avoids having to muck with >>VM layout, etc. >> >> > >Is the CLOCK_* namespace ours to muck about with in the first place ? > > > I prefer this way, can you implement it? The global page idea is a complex, someone can slowly work on it, there are many things can be done, for example, fast syscall using sysenter/sysexit.