This scenario is a mirrored setup. There's no real value in running performance test in both directions. If the test requires testing of reversed scenario it should inherit from PerfReversibleFlowMixin class instead.
Signed-off-by: Jan Tluka jtluka@redhat.com --- lnst/Recipes/ENRT/DoubleTeamRecipe.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/lnst/Recipes/ENRT/DoubleTeamRecipe.py b/lnst/Recipes/ENRT/DoubleTeamRecipe.py index 39e069e5..305ffdeb 100644 --- a/lnst/Recipes/ENRT/DoubleTeamRecipe.py +++ b/lnst/Recipes/ENRT/DoubleTeamRecipe.py @@ -92,8 +92,7 @@ class DoubleTeamRecipe(CommonHWSubConfigMixin, OffloadSubConfigMixin, ]
def generate_perf_endpoints(self, config): - return [(self.matched.host1.team0, self.matched.host2.team0), - (self.matched.host2.team0, self.matched.host1.team0)] + return [(self.matched.host1.team0, self.matched.host2.team0)]
@property def offload_nics(self):