Hide Forgot
In order to make use of and properly test flower scheduler backport in RHEL7 kernel, support for it in 'tc' utility should be backported as well.
Ah, my bad: Flower is not a scheduler, but a classifier.
Jonathan, would you help us identifying the most important test cases? Is there anything specific we should focus on during the testing?
(In reply to Ondrej Moriš from comment #3) > Jonathan, would you help us identifying the most important test cases? Is > there anything specific we should focus on during the testing? Yes I would be happy to review any test plans so that I can make useful suggestions based on what you are already covering. I am currently reviewing the netsched test plan[1]. In general I would focus on basic functionality, for example given 3 tcp streams can flower filter one of those streams and drop/mark it. I would then take this basic test and then attempt to run the same test while trying to have hardware offload the filtering, which some devices can do. These are functional tests however and maybe I am missing the level and type of testing your team needs to do. [1] https://wiki.test.redhat.com/Kernel/Testplans/RHEL74Netsched
Hi Jonathan, I have also written some tests which focus on the basic functionality. In these cases I add some tc rules with most of tc-flower options, send traffic, and then check if the traffic could be matched and dropped successfully. Now it shows that the results of my tests are all passed, so do you think I can set this bz to Verified? Thanks, Shuang
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2171