http://defect.opensolaris.org/bz/show_bug.cgi?id=11784
--- Comment #11 from amaguire <alan.maguire at sun.com> 2009-10-07 16:46:32 UTC --- (In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #8) > > > > nextalarm = e->event_time - now; > > > > if (nextalarm > 0) > > > > (void) alarm(nextalarm) > > > > > > 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. -- 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.
