From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] [sources] applied patch: /n/atom/patch/applied/termrcnodhcp
Date: Tue, 15 Oct 2013 08:58:05 -0400 [thread overview]
Message-ID: <b8441aa47fe01d9206f6a4dc6403f94a@coraid.com> (raw)
In-Reply-To: <20131015133242.BzZtmIHXbY5g5ZxUYrTW3X/A@dietcurd.local>
> then each tick sleeps ~1 second (sometimes a tick needed 3 in the
> tests i've done). But if i add
hmm. can you explain more about the environment, and kernel you
were using? i'd like to correct the kernel timing. sleep(n) must be
fairly accurate. i would define that as accurate to ±1/HZ on an
otherwise unloaded system.
- erik
next prev parent reply other threads:[~2013-10-15 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <250d3e7e5500a6e7d72c8ab3d49f9641@coraid.com>
2013-10-15 12:32 ` Steffen Daode Nurpmeso
2013-10-15 12:58 ` erik quanstrom [this message]
2013-10-15 13:15 ` Steffen Daode Nurpmeso
[not found] ` <ca2e3c3a59e76e71362f34b52b6502fc@coraid.com>
2013-10-15 13:19 ` Steffen Daode Nurpmeso
2013-10-15 13:22 ` 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=b8441aa47fe01d9206f6a4dc6403f94a@coraid.com \
--to=quanstro@labs.coraid.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).