From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] IPv6 stack timing out addresses too soon w/ 1ms system tick?
Date: Sat, 18 Jan 2014 22:10:00 -0000 [thread overview]
Message-ID: <lbeu3f$i7m$1@ger.gmane.org> (raw)
I've got DHCPv6 client code that works great on one target, but on a
second target the IPv6 stack is timing out address assignments way too
soon (long before the lease expiry and long before the DHCPv6 client
thread asks for a lease renewal).
The target where the IPv6 stack times out addresses correctly has a
10ms timer tick. The target where the stack is timing out addresses
too soon has a 1ms timer tick. I have to change my test setup to
quatify "way too soon" but it does look like it might be timing out at
10% of the lease time.
Does the IPv6 stack require that the system timer tick be 10ms?
--
Grant Edwards grant.b.edwards Yow! Uh-oh!! I'm having
at TOO MUCH FUN!!
gmail.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2014-01-18 22:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='lbeu3f$i7m$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).