> > Just to block netperf you can send it SIGSTOP :) > Clever :) One could I suppose achieve the same result by making the remote receive socket buffer size smaller than the UDP message size and then not worry about having to learn the netserver's PID to send it the SIGSTOP. I *think* the semantics will be substantially the same? Both will be drops at the socket buffer, albeit for for different reasons. The "too small socket buffer" version though doesn't require one remember to "wake" the netserver in time to have it send results back to netperf without netperf tossing-up an error and not reporting any statistics. Also, netperf has a "no control connection" mode where you can, in effect cause it to send UDP datagrams out into the void - I put it there to allow folks to test against the likes of echo discard and chargen services but it may have a use here. Requires that one specify the destination IP and port for the "data connection" explicitly via the test-specific options. In that mode the only stats reported are those local to netperf rather than netserver. happy benchmarking, rick jones _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
