netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: Patrick McHardy <kaber@trash.net>, Andrew Morton <akpm@osdl.org>,
	Thomas Cataldo <tomc@compaqnet.fr>,
	linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: Hard freeze with 2.6.10-rc3 and QoS, worked fine with 2.6.9
Date: Wed, 8 Dec 2004 15:32:12 +0100	[thread overview]
Message-ID: <20041208143212.GL1371@postel.suug.ch> (raw)
In-Reply-To: <1102509111.1051.54.camel@jzny.localdomain>

* jamal <1102509111.1051.54.camel@jzny.localdomain> 2004-12-08 07:31
> On Wed, 2004-12-08 at 00:17, Patrick McHardy wrote:
> 
> > I think these tests are a waste of time. struct tcf_police is not
> > userspace-visible, so it's highly unlikely that the tc version matters.
> > Why an old kernel needs to be tested is beyond me. 
> 
> Regression testing. 
> You need both backward and forward compatibility.
> Old kernels must continue to work with new tc for the policer using the
> old syntax.
> new kernels must continue to work with old tc for policer management
> using old syntax.
> Policer existed before any tc action code was written and has a very
> different layout of the structure. User tools and classifiers (accessed
> from user tools) do touch that code.
> These kind of tests constitute about 50% or more of my testing.

I invested some time to ease testing since this was primarly my fault
by overlooking the special case of tcf_police.

I've put together a small testsuite allowing to easly run tests for
multiple versions of iproute2. It can be found at:
	http://people.suug.ch/~tgr/iproute2/tc-testsuite.tar.gz

One simply extracts various iproute2 versions into iproute2/ and
sets KERNEL_INCLUDE if needed for older versions. 'make compile' on
the top level compiles all the versions.

The tests are defined in tests/ and are simple shell scripts and get
invoked for every iproute2 verison in iproute2 with $TC and $IP
set to the version currently being tested. The output of every test
run is stored in results/$TEST.$IPVERSION.out respectively .dmesg.

'make clean' removes all the results again.

'make liststests' lists all the available tests.

'make alltests' runs all the tests.

I've run all the tests on my patch with the following kernels and
iproute2 versions:

 - 2.6.10-rc2-bk13 (actions compiled in)
 - 2.6.10-rc2-bk13-no-act (old policer compiled in)
 - 2.4.28-rc1-bk1

 - iproute2-2.6.9-tgr (with all my patches in)
 - iproute2-2.4.7

iproute-2.6.9 was sucessful with all kernels. I couldn't test with the
old 2.4.7 iproute2 yet since the syntax has changed and I need to adopt
the tests first. I will create better tests and run it on patrick's
patch when I get home.

  reply	other threads:[~2004-12-08 14:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1102380430.6103.6.camel@buffy>
2004-12-07  6:35 ` Hard freeze with 2.6.10-rc3 and QoS, worked fine with 2.6.9 Patrick McHardy
2004-12-07  6:44 ` Andrew Morton
2004-12-07 12:29   ` jamal
2004-12-07 16:59     ` Patrick McHardy
2004-12-07 17:07       ` Thomas Graf
2004-12-07 17:23         ` Patrick McHardy
2004-12-08  4:27           ` jamal
2004-12-08  4:41             ` Jamal Hadi Salim
2004-12-08  5:17               ` Patrick McHardy
2004-12-08 12:31                 ` jamal
2004-12-08 14:32                   ` Thomas Graf [this message]
2004-12-08 14:59                     ` Thomas Graf
2004-12-08 15:06                       ` jamal
2004-12-08 15:05                     ` jamal
2004-12-08 17:30                       ` Thomas Graf
2004-12-08  5:30           ` David S. Miller
2004-12-08 12:04             ` jamal
2004-12-08 16:57               ` Patrick McHardy
2004-12-08 19:30                 ` Stephen Hemminger
2004-12-08 19:49                   ` jamal
2004-12-08 21:21                   ` Patrick McHardy
2004-12-08 22:07                     ` Stephen Hemminger
2004-12-08 22:26                       ` Patrick McHardy
2004-12-08 19:44                 ` 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=20041208143212.GL1371@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=tomc@compaqnet.fr \
    /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).