Hi,
I think it is better to stop creating packets when we hit the size limit of
the queue buffer. By doing this, we are certain that we are not losing any
packets. Furthermore, we don't have to create reservoirs to store these
created packets so that they can be added into the queue when there
Hi,
You could check blocked_ , unblock_on_resume_ and the resume() method
inside ns2.2x/queue/queue.cc. You should wrap your new logic inside a
new queue by exploiting those switches and adding another queue that
will hold all the incoming packets when the primary queue is full
(you'll have
Hi,
I appreciate your feedback. I was thinking on the same lines and think it is
better to block packets at the application layer because of obvious reasons.
I have a question and would be delighted if someone could share some
thoughts on it.
My understanding of the network simulator is that
Hi,
Did you check the TCL binding in the C++ part? The new class should have
a new binding, not the same one as declared for drop-tail.
Regards,
Ilyes Gouta.
Eduardo J. Ortega wrote:
hi:
Don't know if you received my last email, so I'll just write you again:
I already have the OTCL
Hi,
Have a look into the ~/ns-2.x/queue directory. You'll find all sorts
of implementations for different active queues. This include RED, RIO,
PRIO, JOBS, etc.
Implementing a new queue is rather easy actually, you'll have to
inherit from Queue and implement the enque() and deque() methods.
