On Thu, 2020-08-27 at 22:25 +0530, Subhashini Rao Beerisetty wrote:
I have an application which finds the data rate over the PCIe interface. I’m getting the lesser data rate in one of my Linux X86 systems.
Some more description, may be? Do you have a PCIe device reading one RAM buffer and then writing to another RAM buffer? Or does it generate dome data and writes them to a RAM buffer? Presumably it uses DMA? How much is the CPU involved into the process? Are we talking about transferring few kilobytes or gigabytes?
When I change the scaling_governor from "powersave" to "performance" mode for each CPU, then there is slight improvement in the PCIe data rate.
Definitely this makes your CPU(s) run at max speed, but depending on platform and settings, this may also affect C-states. Are the CPU(s) generally idle while you measure, or busy (involved into the test)? You could run 'turbostat' while measuring the bandwidth, to get some CPU statistics (e.g., do C-states happen during the PCI test, how busy are the CPUs).
Parallely I started profiling the workload with perf. Whenever I start running the profile command “perf stat -a -d -p <PID>” surprisingly the application resulted in excellent data rate over PCIe, but when I kill the perf command again PCIe data rate drops. I am really confused about this behavior.Any clues from this behaviour?
Well, one possible reason that comes to mind - you get rid of C-states when you rung perf, and this increases the PCI bandwidth. You can just try disabling C-states (there are sysfs knobs) and check it out. Turbostat could be useful to check for this (with and without perf, run 'turbostat sleep 10' or something like this (measure for 10 seconds in this example), do this while running your PCI test. But I am really just guessing here, I do not know enough about your test and the system (e.g., "a Linux x86" system can be so many things, like Intel or AMD server or a mobile device)...