I agree with Roman, that is the expected behaviour. One thing to add, depending on your requirements you might not need to uniquefy the packet. Setting packet annotations do not require a unique packet, either work directly on the packet itself or clone it and set the clone's annotation.
Beyers On Wed, Dec 9, 2009 at 5:50 PM, Roman Chertov <[email protected]> wrote: > [email protected] wrote: > > > > I have not anderstant exactly how Simple Queue works. > > For a specific use, I patch SimpleQueue to add an annotation when the > > length is greather tha a given value using the packet->uniqueify() > > function to have a new packet to annotate .When the ModifiedQueue is > > empty, nothing special happends. > > > > But when the Queue contains Packets, the CPU usage grows very quickly > > and go to 100% when the numbre of packets in the queue becomes higher; > > When the Queue becomes empty, the CPU usage decrease slowly to a normal > > value > > > > I's a normal behavior for a Simple Queue or is this problem related to > > my patch? > > This is the expected behavior as the router is busy processing packets. > If there are no packets to process, then there is no need to consume > the CPU resources. > > Roman > > > > > > > I use click 1.7 with multithread option. > > > > Help will be welcome > > > > _______________________________________________ > > 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
