On Thu, May 14, 2020 at 11:58:36AM +0200, Jirka Hladky wrote: > Thank you, Mel! > > We are using netperf as well, but AFAIK it's running on two different > hosts. I will check with colleagues, if they can > add network-netperf-unbound run on the localhost. > > Is this the right config? > https://github.com/gormanm/mmtests/blob/345f82bee77cbf09ba57f470a1cfc1ae413c97df/bin/generate-generic-configs > sed -e 's/NETPERF_BUFFER_SIZES=.*/NETPERF_BUFFER_SIZES=64/' > config-network-netperf-unbound > config-network-netperf-unbound-small >
That's one I was using at the moment to have a quick test after the reconciliation series was completed. It has since changed to config-network-netperf-cstate-small-cross-socket to limit cstates, bind the client and server to two local CPUs and using one buffer size. It was necessary to get an ftrace function graph of the wakeup path that was readable and not too noisy due to migrations, cpuidle exit costs etc. -- Mel Gorman SUSE Labs
