Beyers, Thank you. I hope the documentation will be updated to reflect this restriction.
Raja ________________________________ From: Beyers Cronje <[email protected]> To: "[email protected]" <[email protected]> Sent: Wednesday, June 22, 2011 6:16 PM Subject: Re: [Click] click 1.8.0 Unqueue2 -> 100% CPU usage Raja, It does not look like Unqueue2 currently implements any queue notifier signals, where Unqueue does. This explains why you get 100% utilization with Unqueue2 as it will continually check the queue for packets. Unqueue on the other hand listens for queue empty signals and will not reschedule itself if the upstream queue is empty. Beyers On Thu, Jun 23, 2011 at 2:41 AM, R H <[email protected]> wrote: > Hi, > > Using the following sample configuration, I get 100% CPU usage even after > the InfiniteSource finishes sending the 100 packets; but if I replace > Unqueue2 with Unqueue everything works well. Looked at the documentation > and they both default to pulling 1 packet when scheduled until there is > nothing to pull. What am I missing? > > s :: InfiniteSource(\<0800>, RATE 75, LIMIT 100, STOP false); //random > numbers as long as it does not stop! > > q :: NotifierQueue(200); > uq :: Unqueue2(); > p :: Print(); > > d :: Discard; > > s->q->uq->p->d; > > Thanks, > Raja > _______________________________________________ > click mailing list > [email protected] > https://amsterdam.lcs.mit.edu/mailman/listinfo/click > _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
