From: kuznet@ms2.inr.ac.ru
To: davem@redhat.com (David S. Miller)
Cc: mashirle@us.ibm.com, netdev@oss.sgi.com
Subject: Re: [PATCH] Implementation for IPv6 MIB:ipv6AddressTable
Date: Tue, 7 Oct 2003 15:16:20 +0400 (MSD) [thread overview]
Message-ID: <200310071116.PAA30760@yakov.inr.ac.ru> (raw)
In-Reply-To: <20031007034051.3fcb3218.davem@redhat.com> from "David S. Miller" at ïËÔ 07, 2003 03:40:51
Hello!
> Do you think it is large enough for timestamp? :)
If it is not, "unsigned long" is not enough either.
Actually, this does not depend on our implementation. If people implement
a MIB, required precision of these times is prescribed in the rfc.
And this is definitely not jiffies.
Alexey
next prev parent reply other threads:[~2003-10-07 11:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 23:37 [PATCH] Implementation for IPv6 MIB:ipv6AddressTable Shirley Ma
2003-10-07 10:38 ` kuznet
2003-10-07 10:40 ` David S. Miller
2003-10-07 11:16 ` kuznet [this message]
2003-10-07 11:12 ` David S. Miller
2003-10-07 11:35 ` YOSHIFUJI Hideaki / 吉藤英明
-- strict thread matches above, loose matches on Subject: below --
2003-10-07 17:11 Shirley Ma
2003-10-08 18:23 ` Shirley Ma
2003-10-08 18:55 Shirley Ma
2003-10-08 20:00 ` David S. Miller
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=200310071116.PAA30760@yakov.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=davem@redhat.com \
--cc=mashirle@us.ibm.com \
--cc=netdev@oss.sgi.com \
/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).