From: Patrick McHardy <kaber@trash.net>
To: almaop@poczta.fm
Cc: David Miller <davem@davemloft.net>,
"linux-net@vger.kernel.org" <linux-net@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: New filter 'flow' bug?
Date: Wed, 29 Oct 2008 17:46:57 +0100 [thread overview]
Message-ID: <49089381.1030906@trash.net> (raw)
In-Reply-To: <20081029140905.586E4E4357B@f11.poczta.interia.pl>
almaop@poczta.fm wrote:
>>> From: almaop@poczta.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.
next prev parent reply other threads:[~2008-10-29 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 14:09 New filter 'flow' bug? almaop
2008-10-29 16:46 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-05 13:29 almaop
2008-10-30 9:39 almaop
2008-11-03 12:02 ` Patrick McHardy
[not found] <20081029072705.376AC1E3087@f03.poczta.interia.pl>
2008-10-29 7:37 ` David Miller
2008-10-29 8:15 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49089381.1030906@trash.net \
--to=kaber@trash.net \
--cc=almaop@poczta.fm \
--cc=davem@davemloft.net \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).