From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next 0/5] A test for mirror-to-gretap with team in UL packet path Date: Mon, 30 Jul 2018 09:48:25 -0700 (PDT) Message-ID: <20180730.094825.1936294046318747308.davem@davemloft.net> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org, shuah@kernel.org To: petrm@mellanox.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:33054 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726752AbeG3SYR (ORCPT ); Mon, 30 Jul 2018 14:24:17 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Petr Machata Date: Mon, 30 Jul 2018 16:37:17 +0200 > This patchset adds a test for "tc action mirred mirror" where the > mirrored-to device is a gretap, and underlay path contains a team > device. > > In patch #1 require_command() is added, which should henceforth be used > to declare dependence on a certain tool. > > In patch #2, two new functions, team_create() and team_destroy(), are > added to lib.sh. > > The newly-added test uses arping, which isn't necessarily available. > Therefore patch #3 introduces $ARPING, and a preexisting test is fixed > to require_command $ARPING. > > In patches #4 and #5, two new tests are added. In both cases, a team > device is on egress path of a mirrored packet in a mirror-to-gretap > scenario. In the first one, the team device is in loadbalance mode, in > the second one it's in lacp mode. (The difference in modes necessitates > a different testing strategy, hence two test cases instead of just > parameterizing one.) I always like seeing new test cases. :) Series applied, thanks.