From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: Denys <denys@visp.net.lb>,
Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: HTB/act_mirred problem [was: one more... iproute commands lockup whole system]
Date: Wed, 04 Apr 2007 16:50:11 +0200 [thread overview]
Message-ID: <4613BB23.2050507@trash.net> (raw)
In-Reply-To: <1175697202.4063.17.camel@localhost>
jamal wrote:
> On Wed, 2007-04-04 at 16:13 +0200, Patrick McHardy wrote:
>
>>This seems to be due to be caused by act_mirred returning TC_ACT_STOLEN,
>>which is translated to NET_XMIT_SUCCESS within prio, causing HTB to
>>increase the q.qlen counter and activating the class despite no packet
>>beeing queued.
>>
>>Jamal, we can't return NET_XMIT_SUCCESS unless we've really queued the
>>packet. I can't remeber the reason why this is done, could you remind
>>me?
>
>
> IIRC, It had to do with not confusing TCP to try and retransmit.
No, that was the default return code which applies to TC_ACT_SHOT
and unclassified packets (29f1df6cc1c3ee3530939f0e38d80a9b50645ba5).
Returning NET_XMIT_SUCCESS for TC_ACT_STOLEN/TC_ACT_QUEUED has always
been done.
Anyway, we can't return NET_XMIT_SUCCESS, so how about just returning
NET_XMIT_BYPASS in all cases where the packet was stolen/dropped/...
by TC actions?
> I can
> go back and look at my notes to be certain. At one point i posted those
> notes, it maybe time to add them to the kernel code or doc somewhere.
In case they're still up to date, adding them somewhere under
Documentation/ sounds good.
next prev parent reply other threads:[~2007-04-04 14:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 18:00 iproute2-2.6.20-070313 bug ? Denys
2007-03-22 11:23 ` Patrick McHardy
2007-03-22 12:46 ` Denys
2007-03-22 13:09 ` Patrick McHardy
[not found] ` <20070322131245.M85528@visp.net.lb>
2007-03-22 13:23 ` Patrick McHardy
2007-03-22 13:35 ` Denys
[not found] ` <20070322132637.M88445@visp.net.lb>
2007-03-22 13:43 ` Patrick McHardy
2007-03-22 13:47 ` Denys
2007-03-22 13:26 ` Denys
2007-03-22 17:12 ` Stephen Hemminger
2007-03-22 17:14 ` Patrick McHardy
2007-03-26 18:49 ` more... iproute2/htb/whatever critical " Denys
2007-03-27 15:10 ` Patrick McHardy
2007-03-27 15:18 ` Denys
2007-03-27 16:00 ` Denys
2007-03-27 16:21 ` Patrick McHardy
2007-03-28 17:38 ` another " Denys
2007-03-28 23:55 ` Denys
2007-03-29 10:58 ` Patrick McHardy
2007-03-31 2:26 ` more iproute2 issues (not critical) Denys
2007-03-31 2:31 ` Denys
2007-03-31 14:16 ` Patrick McHardy
2007-04-04 0:03 ` one more... iproute commands lockup whole system Denys
2007-04-04 1:10 ` jamal
2007-04-04 1:39 ` Patrick McHardy
2007-04-04 2:09 ` jamal
2007-04-04 2:11 ` Denys
2007-04-04 10:55 ` jamal
2007-04-04 12:56 ` Denys
2007-04-04 14:10 ` jamal
2007-04-04 14:35 ` Denys
2007-04-04 14:13 ` HTB/act_mirred problem [was: one more... iproute commands lockup whole system] Patrick McHardy
2007-04-04 14:33 ` jamal
2007-04-04 14:50 ` Patrick McHardy [this message]
2007-04-05 1:33 ` jamal
2007-04-04 13:36 ` one more... iproute commands lockup whole system Patrick McHardy
2007-04-04 13:58 ` jamal
2007-04-04 14:07 ` Patrick McHardy
2007-04-04 14:30 ` jamal
2007-04-04 14:39 ` Patrick McHardy
2007-04-05 2:14 ` jamal
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=4613BB23.2050507@trash.net \
--to=kaber@trash.net \
--cc=denys@visp.net.lb \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).