From: Jamal Hadi Salim <jhs@mojatatu•com>
To: John Fastabend <john.fastabend@gmail•com>
Cc: john Fastabend <john.r.fastabend@intel•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
Cong Wang <xiyou.wangcong@gmail•com>
Subject: Re: action stats broken?
Date: Sun, 21 Sep 2014 08:33:40 -0400 [thread overview]
Message-ID: <541EC5A4.9040600@mojatatu.com> (raw)
In-Reply-To: <541D9B78.8070505@gmail.com>
On 09/20/14 11:21, John Fastabend wrote:
> On 09/20/2014 06:17 AM, Jamal Hadi Salim wrote:
>
> I'm looking into it which classifier? A basic u32 classifier attached
> to the ingress qdisc seems to work. If your using u32 any hash tables,
> or 'filter change' commands before this?
>
Nothing that exciting.
> # tc actions add action drop index 4
>
> # tc filter add dev p3p1 parent ffff:0 protocol ip prio 100 \
> u32 match ip src 16.0.0.2 action gact index 4
>
> #tc -s actions ls action gact
>
> action order 0: gact action drop
> random type none pass val 0
> index 4 ref 2 bind 1 installed 142 sec used 0 sec
> Action statistics:
> Sent 840 bytes 10 pkt (dropped 10, overlimits 0 requeues 0)
> backlog 0b 0p requeues 0
>
Indeed that looks sane. What kernel version + iproute2?
I have time this morning - I will chase it to double check in case
my environment is messed up.
cheers,
jamal
>> cheers,
>> jamal
>> --
>> To unsubscribe from this list: send the line "unsubscribe netdev" in
>> the body of a message to majordomo@vger•kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2014-09-21 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 13:17 action stats broken? Jamal Hadi Salim
2014-09-20 15:21 ` John Fastabend
2014-09-21 12:33 ` Jamal Hadi Salim [this message]
2014-09-21 14:21 ` Jamal Hadi Salim
2014-09-21 14:50 ` John Fastabend
2014-09-21 15:01 ` Jamal Hadi Salim
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=541EC5A4.9040600@mojatatu.com \
--to=jhs@mojatatu$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=john.r.fastabend@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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