From: EBo <ebo@sandien.com>
To: <9fans@9fans.net>
Subject: Re: [9fans] nsec limits?
Date: Mon, 1 Aug 2011 15:25:16 -0500 [thread overview]
Message-ID: <e3cbb43947d8c8b063271c92f8355e56@swcp.com> (raw)
In-Reply-To: <CAP6exYKm0st1pV8mcPHe2e3E6n8hhOtvGusZqzMh3i+SjvC-tg@mail.gmail.com>
On Mon, 1 Aug 2011 10:17:13 -0700, ron minnich wrote:
> if nsec on whatever platform reads from /dev/bintime, my suggestion
> is
> you not use it. Read from the processor counter instead.
Yes, nsec does call bintime from devcons. Can you point to an example
that uses the process counter? I was trying to avoid using
gettimeofday, and rereading through the devcons code I see that it
sneaks in a call to todget() which IS gettomeofday.
EBo --
next prev parent reply other threads:[~2011-08-01 20:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 12:17 EBo
2011-08-01 12:36 ` erik quanstrom
2011-08-01 13:22 ` EBo
2011-08-01 15:57 ` ron minnich
2011-08-01 17:12 ` EBo
2011-08-01 17:17 ` ron minnich
2011-08-01 20:25 ` EBo [this message]
2011-08-01 22:25 ` Charles Forsyth
2011-08-01 22:51 ` EBo
2011-08-01 23:06 ` ron minnich
2011-08-01 23:31 ` EBo
2011-08-01 23:14 ` Charles Forsyth
2011-08-01 23:19 ` Charles Forsyth
2011-08-01 23:49 ` EBo
2011-08-01 23:25 ` 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=e3cbb43947d8c8b063271c92f8355e56@swcp.com \
--to=ebo@sandien.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).