On Fri, Oct 16, 2015 at 5:19 AM, Jamal Hadi Salim wrote:
>
> Like i said earlier, the idea of keeping track of backlog is useful.
> I think the commit log threw me off.
> "It is odd to see qlen!=0 but backlog==0"
> If you change that commit log then:
Sure, I think DaveM probably already discards
On 10/15/15 00:21, Cong Wang wrote:
On Wed, Oct 14, 2015 at 5:25 AM, Jamal Hadi Salim wrote:
On 10/12/15 14:38, Cong Wang wrote:
It is odd to see qlen!=0 but backlog==0, for a real example:
Backlog is a transient stat so a lot of times it should be 0. Only when
the CPU is sending faster th
On Wed, Oct 14, 2015 at 5:25 AM, Jamal Hadi Salim wrote:
> On 10/12/15 14:38, Cong Wang wrote:
>>
>> It is odd to see qlen!=0 but backlog==0, for a real example:
>>
>
> Backlog is a transient stat so a lot of times it should be 0. Only when
> the CPU is sending faster than the link can handle shou
On 10/12/15 14:38, Cong Wang wrote:
It is odd to see qlen!=0 but backlog==0, for a real example:
Backlog is a transient stat so a lot of times it should be 0. Only when
the CPU is sending faster than the link can handle should you see
the backlog grow (and eventually drain to 0).
Even though
It is odd to see qlen!=0 but backlog==0, for a real example:
qdisc htb 1: dev eth0 root refcnt 2 r2q 10 default 1 direct_packets_stat 0 ver
3.17
Sent 172680457356 bytes 222469449 pkt (dropped 0, overlimits 123575834
requeues 0)
backlog 0b 72p requeues 0
So we need to update backlog too when w
