Linux Test Project
 help / color / mirror / Atom feed
From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v8 0/3] networking/stress/icmp: add ip xfrm ipsec support
Date: Thu, 28 Apr 2016 16:51:14 +0300	[thread overview]
Message-ID: <57221552.8050507@oracle.com> (raw)
In-Reply-To: <1461761676-28599-1-git-send-email-haliu@redhat.com>

Hi,
On 04/27/2016 03:54 PM, Hangbin Liu wrote:
> As we know, most of the network stress tests have IPsec testing, and we use
> setkey for configuration. But setkey[1] hasn't updated for a long time. And
> some distros, RHEL7 for example, even don't have ipset-tools package. On
> other hand, iproute2 is recommend for network configuration. And ip xfrm is
> more powerful than setkey. So let's use ip xfrm for ipsec testing.
>
> [1] http://ipsec-tools.sourceforge.net/
>
> Change from V7:
> 1. correct array typo
> 2. use shift instead of bashism
Patch-set applied, thank you.

Also made some cosmetic changes:

* reworded that really lengthy message with "Verify that kernel ...." in 
icmp-basic-uni,
* added suffix ".sh" to icmp-uni-basic,
* some lines were over 80 chars, changed them too where possible,
* added copyright line from the previous version of uni-basic tests,
* removed old uni-basic directory.

Thanks,
Alexey


  parent reply	other threads:[~2016-04-28 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 12:54 [LTP] [PATCH v8 0/3] networking/stress/icmp: add ip xfrm ipsec support Hangbin Liu
2016-04-27 12:54 ` [LTP] [PATCH v8 1/3] lib/test_net.sh: add tst_ping() to check icmp connectivity Hangbin Liu
2016-04-27 12:54 ` [LTP] [PATCH v8 2/3] network/stress: add ipsec lib Hangbin Liu
2016-04-27 12:54 ` [LTP] [PATCH v8 3/3] network/stress/icmp: add icmp-uni-basic to implement all icmp basic stress test Hangbin Liu
2016-04-28 13:51 ` Alexey Kodanev [this message]
2016-04-29  2:05   ` [LTP] [PATCH v8 0/3] networking/stress/icmp: add ip xfrm ipsec support Hangbin Liu

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=57221552.8050507@oracle.com \
    --to=alexey.kodanev@oracle.com \
    --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