[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <490EE873.6040305@trash.net>
Date: Mon, 03 Nov 2008 13:02:59 +0100
From: Patrick McHardy <kaber@...sh.net>
To: almaop@...zta.fm
CC: "linux-net@...r.kernel.org" <linux-net@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: New filter 'flow' bug?
almaop@...zta.fm wrote:
>> almaop@...zta.fm wrote:
>>>>> From: almaop@...zta.fm
>>>>>> I'm not sure where is the bug - in the flow filter or in the sfq
>>>> qdisc.
>>>>
>>>> Which SFQ qdisc is stalling?
>>>>
>>> Thanks for reply.
>>> So I've done few tests. I've removed quantum 64 (it was qdisc with
>> small packets). It made no difference. It looks like the key is the first
>> sfq qdisc (tc qdisc add dev $DEV parent 1:2 handle 2: sfq - in my example).
>> When there is no traffic in this qdisc for about 45 seconds (shorter time
>> when there is no traffic at all on the interface) - it stalls. Other qdiscs
>> stall also. So there is no packet flow on that interface. Removing filters
>> ('flow' filters) does'nt help. I have to remove (all) sfq qdiscs. And then
>> the traffic is resumed.
>>
>> Please capture the output of "tc -s -d qdisc show dev <dev>" and
>> "tc -s -d class show dev <dev>" immediately after it stalls.
>> I'm interested in the amount of bytes/packets queued at the moment.
>>
>
> I've captured it eve
> It looks like this:
> Example 1:
>
> ...
In both cases there are no packets queued, so its not the qdiscs
which are stalling. My shot in the dark is is that your classifier
rules are incorrect and don't handle ARP packets.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists