update CHANGES.html for Queue::Enqueue trace behavior change
authorCraig Dowell <craigdo@ee.washington.edu>
Mon, 17 May 2010 14:31:20 -0700
changeset 6308 2ca5ef07be74
parent 6307 6ac5cd5ec178
child 6309 8d46400b959e
update CHANGES.html for Queue::Enqueue trace behavior change
CHANGES.html
--- a/CHANGES.html	Mon May 17 07:29:43 2010 -0700
+++ b/CHANGES.html	Mon May 17 14:31:20 2010 -0700
@@ -67,6 +67,14 @@
 
 <h2>Changed behavior:</h2>
 <ul>
+<li><b>Queue trace behavior during Enqueue changed:</b> The behavior of the
+Enqueue trace source has been changed to be more intuitive and to agree with
+documentation.  Enqueue and Drop events in src/node/queue.cc are now mutually
+exclusive.  In the past, the meaning of an Enqueue event was that the Queue
+Enqueue operation was being attempted; and this could be followed by a Drop
+event if the Queue was full.  The new behavior is such that a packet is either
+Enqueue'd successfully or Drop'ped.
+
 <li><b>Drop trace logged for Ipv4/6 forwarding failure:</b> Fixed bug 861; this 
 will add ascii traces (drops) in Ipv4 and Ipv6 traces for forwarding failures
 </ul>