Page MenuHomeFreeBSD

altq tests: Basic ALTQ test
ClosedPublic

Authored by kp on Jan 23 2021, 10:52 AM.
Tags
None
Referenced Files
F108517045: D28303.id82852.diff
Sat, Jan 25, 7:56 PM
F108511890: D28303.id82763.diff
Sat, Jan 25, 7:14 PM
F108511813: D28303.id82870.diff
Sat, Jan 25, 7:13 PM
Unknown Object (File)
Thu, Jan 23, 8:27 PM
Unknown Object (File)
Fri, Jan 3, 10:38 AM
Unknown Object (File)
Dec 22 2024, 8:50 PM
Unknown Object (File)
Dec 4 2024, 8:25 PM
Unknown Object (File)
Nov 26 2024, 6:00 PM

Details

Summary

Activate ALTQ_HFSC, crudely check if it really limits bandwidth as we'd expect.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kp requested review of this revision.Jan 23 2021, 10:52 AM
donner added inline comments.
tests/sys/netpfil/pf/altq.sh
26

It's expected, that this command always succeed, so there is no check needed. Correct?

38

There is a race condition between the "saturate" ping and the test. A busy system might have several seconds between those commands.

Would it be possible to rephrase the check, so that the ping is sending i.e. 10 packets and we expect 3 of them back?

Adjust to new altq.foo sysctl

This revision is now accepted and ready to land.Jan 25 2021, 3:23 PM
This revision was automatically updated to reflect the committed changes.