9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sleep(2) historical question
Date: Wed, 28 Nov 2012 13:43:55 -0800	[thread overview]
Message-ID: <20121128214355.4641AB85C@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 28 Nov 2012 20:58:03 GMT." <CAOw7k5ikb-TMt_hDiY3=1699xKwAe+9gP1n2_pHgrpTEYAwsKg@mail.gmail.com>

On Wed, 28 Nov 2012 20:58:03 GMT Charles Forsyth <charles.forsyth@gmail.com>  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.



  parent reply	other threads:[~2012-11-28 21:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 23:19 erik quanstrom
2012-11-28  7:37 ` Charles Forsyth
2012-11-28 12:57   ` erik quanstrom
2012-11-28 13:10     ` Charles Forsyth
2012-11-28 13:30       ` erik quanstrom
2012-11-28 14:35         ` Charles Forsyth
2012-11-28 14:46           ` erik quanstrom
2012-11-28 18:58         ` Bakul Shah
2012-11-28 19:10           ` Charles Forsyth
2012-11-28 19:28             ` erik quanstrom
2012-11-28 18:56               ` cinap_lenrek
2012-11-28 19:38             ` Bakul Shah
2012-11-28 20:58               ` Charles Forsyth
2012-11-28 21:02                 ` erik quanstrom
2012-11-28 21:13                   ` Charles Forsyth
2012-11-28 21:19                     ` erik quanstrom
2012-11-28 21:21                     ` erik quanstrom
2012-11-28 21:43                 ` Bakul Shah [this message]
2012-11-29  0:12                   ` Charles Forsyth
2012-11-29  8:12                   ` arnold
2012-11-29  9:19                     ` Charles Forsyth
2012-11-29 15:17                       ` erik quanstrom
2012-11-28 19:27           ` David Arnold
2012-11-28 21:12             ` Charles Forsyth
2012-11-28 19:29           ` erik quanstrom
2012-11-28 19:54             ` Bakul Shah
2012-11-28 19:57               ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121128214355.4641AB85C@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).