http://defect.opensolaris.org/bz/show_bug.cgi?id=11784
--- Comment #13 from Michael Hunter <michael.hunter at sun.com> 2009-10-07 17:04:41 UTC --- (In reply to comment #11) [...] > > > > This makes sense; but we need to be sure we don't lose that next > > > > pending event. > > > > How does it get handled if we don't schedule another alarm? We will > > > > pull it > > > > off and process it (enqueue it on the event queue?) right here? > > > > > > In the above code snippet, we don't set the alarm if the alarm is > > > scheduled to > > > go off within this second. > > > > Consider something that is suppose to go off at time 0 and time 0.9. They > > will > > both look like 0 and thus we will (or should have) scheduled the event > > contradicting your statement. > > But events are scheduled in units of seconds - nwamd_event_enqueue_timed() > takes a uint32_t "when" argument specifying the number of seconds in which the > event will be enqueued. If 0 is passed in for "when", we just call > nwamd_event_enqueue() directly. Yea, but now is, well, now. That is wall clock. You schedule an integral number of second but not from an integral number of second. -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
