[Codel] queue-size(in terms of packets) for codel in ns-2.35

[Codel] queue-size(in terms of packets) for codel in ns-2.35

[mandy ahuja]

[-- Attachment #1: Type: text/plain, Size: 430 bytes --]

Hi All
i read that queue- size sould be set according to BDP.

But when we calculate BDP=Bandwidth*Delay
                                         =b/s*s
                                          =b
                                           =b/8(B)

So it is in terms of bytes or bits.

But in NS2 we can set queue-size in terms of packet only.
"$ns queue-limit no_of_packets"

So anybody please tell   how can i set it??

Thanks

[-- Attachment #2: Type: text/html, Size: 740 bytes --]

Re: [Codel] queue-size(in terms of packets) for codel in ns-2.35

[Jonathan Morton]

[-- Attachment #1: Type: text/plain, Size: 590 bytes --]

If you know the size of the packets that will be using it, then it is
simple to cover from one to the other. That's more likely in a simulator
than the real world though.

IIRC, TCP acks are usually 48 bytes, but this may vary if extension options
and/or IPv6 are in use. Check this yourself on the traffic you're testing.
In the forward data flow direction, expect most packets to be at the link
segment size limit, 1500 bytes for Ethernet.

But if you have heterogeneous or bidirectional traffic, this calculation
breaks down. This may simply be one limitation of ns2.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 674 bytes --]

Re: [Codel] queue-size(in terms of packets) for codel in ns-2.35

[mandy ahuja]

[-- Attachment #1: Type: text/plain, Size: 736 bytes --]

By knowing the packet size, next what??

On Sun, Mar 1, 2015 at 7:19 AM, Jonathan Morton <chromatix99@gmail.com>
wrote:

> If you know the size of the packets that will be using it, then it is
> simple to cover from one to the other. That's more likely in a simulator
> than the real world though.
>
> IIRC, TCP acks are usually 48 bytes, but this may vary if extension
> options and/or IPv6 are in use. Check this yourself on the traffic you're
> testing. In the forward data flow direction, expect most packets to be at
> the link segment size limit, 1500 bytes for Ethernet.
>
> But if you have heterogeneous or bidirectional traffic, this calculation
> breaks down. This may simply be one limitation of ns2.
>
> - Jonathan Morton
>

[-- Attachment #2: Type: text/html, Size: 1148 bytes --]

Re: [Codel] queue-size(in terms of packets) for codel in ns-2.35

[Jonathan Morton]

[-- Attachment #1: Type: text/plain, Size: 267 bytes --]

Elementary arithmetic, my dear.

Or, specifically for Codel (rather than drop tail), you could just make it
a big number like 10000 to get it out of the way. Codel will generally get
control of the queue back long before that sort of limit is hit.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 322 bytes --]

Re: [Codel] queue-size(in terms of packets) for codel in ns-2.35

[mandy ahuja]

[-- Attachment #1: Type: text/plain, Size: 424 bytes --]

yeah actually it is. dividing by packet size.
anywayz thanks

On Sun, Mar 1, 2015 at 10:11 PM, Jonathan Morton <chromatix99@gmail.com>
wrote:

> Elementary arithmetic, my dear.
>
> Or, specifically for Codel (rather than drop tail), you could just make it
> a big number like 10000 to get it out of the way. Codel will generally get
> control of the queue back long before that sort of limit is hit.
>
> - Jonathan Morton
>

[-- Attachment #2: Type: text/html, Size: 832 bytes --]