From mboxrd@z Thu Jan 1 00:00:00 1970 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-reply-to: Your message of "Wed, 28 Nov 2012 20:58:03 GMT." References: <0263c93c2d57900638e664f1b538a76d@brasstown.quanstro.net> <0cf8de222eb5fa81721e8bcf4dd4e875@brasstown.quanstro.net> <20121128185827.863CFB827@mail.bitblocks.com> <20121128193840.29418B827@mail.bitblocks.com> Date: Wed, 28 Nov 2012 13:43:55 -0800 From: Bakul Shah Message-Id: <20121128214355.4641AB85C@mail.bitblocks.com> Subject: Re: [9fans] sleep(2) historical question Topicbox-Message-UUID: edd6bdde-ead7-11e9-9d60-3106f5b1d025 On Wed, 28 Nov 2012 20:58:03 GMT Charles Forsyth wrote: > RTT computation isn't the problem. you're going to use a multicore > numa 64-bit processor to clock edges into a simple device register at > microsecond resolution without any attempt at timeliness? seriously? Not everyone is running plan9 on multicore numa machines! I want to run it specifically on low end machines, *for* hardware control among other things. Other OS choices here are not as palatable. By your argument why even 100Hz? Why not have a 1sec clock? If a finer resolution timers were provided, may be that'd be an incentive to fix any plan9 issues with scheduling or accuracy. And I think fixing such issues will be *easier* in plan9 than in Linux or BSD. And in any case why stick to an artificial choice made decades ago when it gets in the way of at lease some applications? Seems best to get rid of the fixed 100Hz clock and allow as fine a timer resolution (& accuracy) as a particular CPU + kernel combination can do.