All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v4 0/3] Simplify network setup
Date: Fri, 7 Apr 2017 14:04:43 +0300	[thread overview]
Message-ID: <7ec9883c-7b9a-42ff-b49f-a5732d59a9fb@oracle.com> (raw)
In-Reply-To: <20170406155005.smxqad2aqkcwecmz@dell5510>

On 06.04.2017 18:50, Petr Vorel wrote:
> ...
>> Given that the number of such tests are really small (stress/route,
>> stress/multicast) and they don't source test_net.sh (only through
>> network.sh), may be it is time to get rid of these variables inside
>> test_net.sh and use just one, for reverse addresses as well?
> testcases/network/stress/dns/dns-stress sources test_net.sh. I suppose we can
> "fix it" by removing test_net.sh and setting necessary variables directly in
> the script like other scripts do (e.g.
> testcases/network/stress/route/route6-change-dst).
> I agree that this would simplify things greatly (tst_net_vars.c would be much
> smaller and use mainly glibc network related functions), but on the other hand I
> wanted all network tests using test_net.sh. I don't like the idea that part of
> the tests which are using the same variables, but their values are hardwired
> into the script.

And if we convert them to use test_net.sh and add missing interfaces
like the ones
needed for dns-stress tests, i.e. tst_ip_reverse(), etc., there would be
no need to
use them directly in the tests.

Actually, we can still update tst_ipaddr() to use IP_HOSTs variables
without adding
together two variables :)

I guess subnet mask should be set as a separate variable, similar to
stress/multicast
tests (to support these tests), and if not provided, we can get it with
getifaddr(), or at
least set to predefined default value, for IPv6 it is almost always /64.

Thanks,
Alexey


  reply	other threads:[~2017-04-07 11:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 20:44 [LTP] [RFC PATCH v4 0/3] Simplify network setup Petr Vorel
2017-04-05 20:44 ` [LTP] [RFC PATCH v4 1/3] gitignore: Prefixing filenames Petr Vorel
2017-04-05 20:44 ` [LTP] [RFC PATCH v4 2/3] network: Add tool for setup IP variables Petr Vorel
2017-04-10 10:36   ` Alexey Kodanev
2017-04-10 13:09     ` Petr Vorel
2017-04-05 20:44 ` [LTP] [RFC PATCH v4 3/3] network: Use tst_net_vars to set up IPv4 and IPv6 related variables Petr Vorel
2017-04-06 14:42 ` [LTP] [RFC PATCH v4 0/3] Simplify network setup Alexey Kodanev
2017-04-06 15:50   ` Petr Vorel
2017-04-07 11:04     ` Alexey Kodanev [this message]
2017-04-10 12:53       ` Petr Vorel
2017-04-10 17:49         ` Alexey Kodanev
2017-04-11  8:50           ` Alexey Kodanev
2017-04-13  9:33             ` Petr Vorel
2017-04-18 16:34           ` Petr Vorel
2017-04-14  9:12   ` Petr Vorel
2017-04-14  9:17     ` Petr Vorel
2017-04-14  9:44       ` Alexey Kodanev
2017-04-14 12:16         ` Petr Vorel

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=7ec9883c-7b9a-42ff-b49f-a5732d59a9fb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.