From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>,
netdev@oss.sgi.com
Subject: Re: [PATCH] PKT_SCHED: Provide compat policer stats in action policer
Date: Tue, 21 Dec 2004 01:16:21 +0100 [thread overview]
Message-ID: <20041221001621.GY17998@postel.suug.ch> (raw)
In-Reply-To: <1103552830.1049.355.camel@jzny.localdomain>
* jamal <1103552830.1049.355.camel@jzny.localdomain> 2004-12-20 09:27
> I just stared quickly at what Thomas has and realize its not really
> automated. In my case it is easier because i can click on the proverbial
> one-button and run 20 tests (including a subset of the policer ones)
> and even capturing tcpdumps. I have attached a sample testcase.
I've put up a snapshot of what I have at:
http://people.suug.ch/~tgr/tmp/tc-testsuite.tar.gz
.. and a special for jamal not including iproute2 sources
so you can save a few bucks ;->
http://people.suug.ch/~tgr/tmp/tc-testsuite-jamal.tar.bz2
I'm not sure what you mean, it's all automated and actually
quite similar to what you've included. Actually, we could
simply run your testscript under my testsuite if you
replace the "tc" with a variable given to the script.
My indev test: (requires a patched iproute2 to correctly
print [ indev INDEV ] in usage text, patches follow later)
----
#!/bin/bash
# vim: ft=sh
#
source lib/generic.sh
TYPE=$1; shift
FILTER=$@
HELP=`$TC filter add ${TYPE} help 2>&1`
if [ "`echo $HELP | grep \"indev DEV\"`" ]; then
if [ $CONFIG_NET_CLS_IND ]; then
ts_tc "attr-indev" "filter addition" $FILTER indev "eth1"
else
ts_log "attr-indev: No INDEV support, checking error return value"
RES=`$TC $FILTER indev "eth1" 2>&1`
if [ "`echo $RES | head -1`" != \
"RTNETLINK answers: Operation not supported" ]; then
echo "Warning: Kernel did not report EOPNOTSUPP"
fi
fi
else
# no support for indev, add filter anyway to not break deletion
ts_log "ip version doesn't support indev, skipping"
ts_tc "attr-indev" "dummy addition" $FILTER
fi
---
Here's an example run:
tgr:axs ~/dev/tc-testsuite make alltests
Running cls-testbed.t [iproute2-2.4.7/2.6.10-rc3-bk12]: FAILED
Running cls-testbed.t [iproute2-2.6.9/2.6.10-rc3-bk12]: PASS
Running dsmark.t [iproute2-2.4.7/2.6.10-rc3-bk12]: FAILED
Running dsmark.t [iproute2-2.6.9/2.6.10-rc3-bk12]: PASS
Running std-cbq.t [iproute2-2.4.7/2.6.10-rc3-bk12]: PASS
Running std-cbq.t [iproute2-2.6.9/2.6.10-rc3-bk12]: PASS
tgr:axs ~/dev/tc-testsuite
So, 2 of them failed, let's see what happenend:
tgr:axs ~/dev/tc-testsuite cat results/cls-testbed.t.iproute2-2.4.7.out
...
Preparing classifier testbed with qdisc dsmark
cls-testbed: dsmark root qdisc creation failed:
command: iproute2/iproute2-2.4.7/tc/tc qdisc add dev lo root handle 10:0 dsmark indices 64 default_index 1 set_tc_index
stderr output:
Unknown qdisc "dsmark", hence option "indices" is unparsable
...
I'll take a closer look at tcng to see how we can put the best parts of both together.
It will definitely be no problem to integrate your expect based tests.
next prev parent reply other threads:[~2004-12-21 0:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 13:01 [PATCH] PKT_SCHED: Provide compat policer stats in action policer Thomas Graf
2004-12-15 14:09 ` jamal
2004-12-15 15:22 ` Thomas Graf
2004-12-15 15:42 ` Patrick McHardy
2004-12-19 19:24 ` jamal
2004-12-20 10:17 ` Patrick McHardy
2004-12-20 14:03 ` Thomas Graf
2004-12-20 14:32 ` jamal
2004-12-20 14:27 ` jamal
2004-12-21 0:16 ` Thomas Graf [this message]
2004-12-22 13:10 ` jamal
2004-12-22 13:32 ` Thomas Graf
2004-12-22 13:54 ` jamal
2004-12-21 10:11 ` Patrick McHardy
2004-12-20 23:51 ` David S. Miller
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=20041221001621.GY17998@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.com \
/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).