Kacheong Poon wrote:
On 09/ 7/10 09:31 PM, Brian Ruthven - Solaris Network Sustaining -
Oracle UK wrote:
It seems that the pkt_stime is the time the packet should be sent, so it
is possible for this to be "in the future" according to cur_time, and
suggests to me that the timeout functionality is broken, unless the
delay is smaller than an lbolt increment (such that pkt_stime ==
cur_time).
The timeout function is set to fire at pkt_stime (in lbolt). When
the timeout function executes, the current time in lbolt should
be >= pkt_stime, hence the check. If the pkt_stime is still in the
future, either lbolt wraps around or the timeout function fires
earlier than it is scheduled. Something is strange in your system.
Ah I see. I should have spotted this :-(
I'm running on a T5240.
I'll check it out and log a bug if necessary.
Does anybody else have any experience of using hxbt with delays such as
200ms or above, or with the timeout/delay code?
There is no warning.
I was afraid of that. I'll adjust the code to work around my "faulty"
hardware.
Thanks,
Brian
--
Brian Ruthven
Solaris Network RPE (Sustaining)
Oracle UK
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org
