From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 0/2] Rewrite route stress tests into C
Date: Tue, 29 Jan 2019 19:18:56 +0100 [thread overview]
Message-ID: <20190129181856.GA17728@dell5510> (raw)
In-Reply-To: <cd8be415-a4e0-06ac-997a-4195b396fa47@oracle.com>
Hi Alexey,
thanks for your comments.
> > Some issues:
> > * The test is only on lhost, no attempt to set iface on rhost and check
> > connection. The only check is done via error of libnl used. It's
> > questionable whether this way is good enough.
> True, it would be better to verify that the route is working and usable.
> At least, we could open a socket and send something using the route
> (ns-udpsender way)...
OK, I'll try at least this. And if it's not suitable enough, I'll have to get
back to shell (or I'd have to implement tst_rhost_run() in C).
> > If we want to have established connection, it'd be better to get back to
> > shell testing [1], just replace netstress to new tool (I'd prefer not
> > use ns-udpsender).>
> > * rtnetlink is used via libnl, which is very lazy approach.
> > As subject of testing is route testing and not rtnetlink testing I
> > didn't reimplement rtnetlink socket communication from scratch, but I
> > guess I should. Also using link caching (used by functions from libnl-cli)
> > might not be a good idea (maybe using libmnl or only libnl-route would
> > be better if using library).
> And libmnl has an example:
> https://git.netfilter.org/libmnl/tree/examples/rtnl/rtnl-route-add.c
I noticed this as well, I'll use libmnl.
Kind regards,
Petr
prev parent reply other threads:[~2019-01-29 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 16:17 [LTP] [RFC PATCH 0/2] Rewrite route stress tests into C Petr Vorel
2019-01-24 16:17 ` [LTP] [RFC PATCH 1/2] tst_net: Add missing includes, make functions inline Petr Vorel
2019-01-24 16:17 ` [LTP] [RFC PATCH 2/2] net/route: Rewrite route{4, 6}-change-dst into C Petr Vorel
2019-01-29 16:38 ` [LTP] [RFC PATCH 0/2] Rewrite route stress tests " Alexey Kodanev
2019-01-29 18:18 ` Petr Vorel [this message]
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=20190129181856.GA17728@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