Date: Mon, 30 Apr 2007 22:42:17 +0200 From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Robert Watson <rwatson@FreeBSD.org> Cc: current@freebsd.org, Hartmut Brandt <Hartmut.Brandt@dlr.de>, Tim Kientzle <kientzle@freebsd.org>, David G Lawrence <dg@dglawrence.com>, "Jesper B. Rosenkilde" <jbr@humppa.dk> Subject: Re: Suggestions on Avoiding syscall Overhead Message-ID: <86bqh5ppau.fsf@dwp.des.no> In-Reply-To: <20070428121554.T28395@fledge.watson.org> (Robert Watson's message of "Sat, 28 Apr 2007 12:23:12 %2B0100 (BST)") References: <f126fae00704221639l68095de1ye7ce9ba3d921bf20@mail.gmail.com> <20070423113400.GC28587@gw.humppa.dk> <462CD251.9060105@freebsd.org> <20070423161711.GV39474@elvis.mu.org> <462D821F.6030707@freebsd.org> <20070424042102.GI38475@tnn.dglawrence.com> <86veflholn.fsf@dwp.des.no> <20070428113752.A28395@fledge.watson.org> <4633299B.2020206@dlr.de> <20070428121554.T28395@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson <rwatson@FreeBSD.org> writes: > Unfortunately, this sort of thing can't be expressed using the > standard APIs. This leaves us two choices: allow the behavior of > standard APIs to be configured at some granularity, or introduce new > APIs. My feeling is we should prefer new APIs, and suggest that > programmers use those. Take a look at sys/sys/time.h:1.71 for an > example of what might make sense. I'm not sure this is a good example. There is already a suitable extensible API: clock_gettime(), which is part of SUSv3. Define new CLOCK_* constants for requesting a faster, less precise timecounter, and if you feel like it, submit it to X/Open for inclusion in the next version of the SUS. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86bqh5ppau.fsf>