From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 4/6] network/mpls02: new test with lwtunnel
Date: Wed, 7 Nov 2018 18:36:16 +0100 [thread overview]
Message-ID: <20181107173615.GA12378@dell5510> (raw)
In-Reply-To: <14316198-1a4b-ad70-5ff3-295b75f5faf9@oracle.com>
Hi Alexey,
> >> + ROD modprobe mpls_router
> >> + ROD modprobe mpls_iptunnel
> >> + ROD modprobe mpls_gso
> > Maybe just?
> > ROD modprobe mpls_gso $TST_NEEDS_DRIVERS
> OK, and it will need the '-a' option.
I wonder if we want to have a simple helper in tst_net.sh for loading modules on
both sides, similar to tst_set_sysctl and tst_net_driver (from my pull request):
tst_net_driver()
{
ROD modprobe -a $@
tst_rhost_run -c "modprobe -a $@"
}
Kind regards,
Petr
next prev parent reply other threads:[~2018-11-07 17:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 13:03 [LTP] [PATCH 0/6] network: new tests for mpls over gre, gre6 and sit Alexey Kodanev
2018-10-29 13:03 ` [LTP] [PATCH 1/6] network/virt: add support for sit tunnel Alexey Kodanev
2018-10-29 13:03 ` [LTP] [PATCH 2/6] network/sit01: new test " Alexey Kodanev
2018-10-29 13:03 ` [LTP] [PATCH 3/6] network/mpls01: new test for mpls labels Alexey Kodanev
2018-10-29 13:03 ` [LTP] [PATCH 4/6] network/mpls02: new test with lwtunnel Alexey Kodanev
2018-11-02 20:02 ` Petr Vorel
2018-11-06 15:30 ` Alexey Kodanev
2018-11-07 17:36 ` Petr Vorel [this message]
2018-11-08 12:34 ` Alexey Kodanev
2018-11-08 14:01 ` Petr Vorel
2018-10-29 13:03 ` [LTP] [PATCH 5/6] network/mpls03: add MPLS over GRE and GREv6 Alexey Kodanev
2018-11-02 20:13 ` Petr Vorel
2018-10-29 13:03 ` [LTP] [PATCH 6/6] network/mpls04: new test with mpls over sit tunnel Alexey Kodanev
2018-11-02 20:15 ` [LTP] [PATCH 0/6] network: new tests for mpls over gre, gre6 and sit Petr Vorel
2018-11-13 15:11 ` Alexey Kodanev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181107173615.GA12378@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox