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 11:38:40 -0800 [thread overview]
Message-ID: <20121128193840.29418B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 28 Nov 2012 19:10:19 GMT." <CAOw7k5iaYTkyXL4WrVyeVEU4daEWKYxxN_AQhd0nRFsexctJJg@mail.gmail.com>
On Wed, 28 Nov 2012 19:10:19 GMT Charles Forsyth <charles.forsyth@gmail.com> wrote:
> No, I don't think it is, in this case. I really don't see many
> applications deeply yearning for tiny sleeps and naplets.
>
> On 28 November 2012 18:58, Bakul Shah <bakul@bitblocks.com> wrote:
> > Chicken and egg.
I wrote a packet traffic/protocol simulator where a 250Hz
clock (seemed to be the default on Linux) was not fast enough.
On FreeBSD I could just up the clock to 10Khz. RTT
computation as Erik pointed out. If you want to minimize
latency in usermode drivers and deal with simple(r) hardware.
Lots of uses.
next prev parent reply other threads:[~2012-11-28 19:38 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 [this message]
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
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=20121128193840.29418B827@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).