BTW, old kernel in this case implies one that does not support tc
actions at all. So pick something like 2.4.28.
New is whatever 2.6.x with patch.
Old tc is something that for example ships with redhat
new tc is whatever one is patched.
Supplementary tests are: in 2.6.x to compile the policer
in two different ways a) via tc actions and b) using the old scheme
which is understood by "old" tc. Repeat the tests i described earlier
with b) pretending to be "old" kernel.
Infact come to think of it i would also prefer to have the suplementary
tests run as well.
If you guys have no cycles, please pass the patch to me and i will test
on the weekend.
On Tue, 2004-12-07 at 23:27, jamal wrote:
> On Tue, 2004-12-07 at 12:23, Patrick McHardy wrote:
> > Either one is fine with me, although I would prefer to see
> > the number of ifdefs in this area going down, not up :)
> You guys pick one or other or a mix. I run 4 base testcases for the
> policer typically:
> 1) Old kernel, uptodate TC - MUST pass
> 2) old kernel, old tc (trivial - expected to pass).
> 3) New Kernel, uptodate TC - MUST pass
> 4) New Kernel, uptodate TC - MUST pass (although trivial)
> Try both setting, dumping then deleting policies.
> If these tests pass, please push patch to Dave.