On Tue, Apr 18, 2017 at 12:20:28PM +0200, Jiri Pirko wrote:
Tue, Apr 18, 2017 at 12:18:36PM CEST, liali(a)redhat.com wrote:
>When i running qos-005, it always print a error: RPC connection to machine machine1
>2017-04-18 05:38:38 (machine1) - DEBUG: Executing: "echo
"start" > /proc/net/pktgen/pgctrl"
>2017-04-18 05:39:34 (machine1) - DEBUG: Killing command with pid
>2017-04-18 05:39:34 (localhost) - INFO: Result: FAIL
>2017-04-18 05:39:34 (localhost) - INFO: Status message from slave:
"RPC connection to machine machine1 timed out"
>Is this because the lnst-slave machine1 is too busy(because it is generating traffic)
so the lnst-ctl lost connection to it?
>If i reduce the pktgen's thread count, this error will disappear. But then it
can't generate enough traffic to make ETS to take effect.
>Anyone encountered this error ?
Ccing LNST people.
LNST-developers mailing list -- lnst-developers(a)lists.fedorahosted.org
To unsubscribe send an email to lnst-developers-leave(a)lists.fedorahosted.org
never encountered this before.
One idea that comes to mind is whether or not the device used for the
Controller-Slave connection is affected by the packet generator.
On principle, this should be a completely isolated NIC, not used for
testing, so if you have some spare cpu cycles left, I don't see an
obvious reason why the connection would time out.