[USRP-users] Installing PCIE drivers for x310

Jared Dulmage jared.dulmage at aero.org
Tue Oct 27 19:42:21 EDT 2015


Trip,

> cpuinfo
Intel(R) Xeon(R)  CPU E5-2640 0 
=====  Processor composition  =====
Processors(CPUs)  : 12
Packages(sockets) : 1
Cores per package : 6
Threads per core  : 2
=====  Processor identification  =====
Processor	Thread Id.	Core Id.	Package Id.
0       	0   		0   		0   
1       	0   		1   		0   
2       	0   		2   		0   
3       	0   		3   		0   
4       	0   		4   		0   
5       	0   		5   		0   
6       	1   		0   		0   
7       	1   		1   		0   
8       	1   		2   		0   
9       	1   		3   		0   
10      	1   		4   		0   
11      	1   		5   		0   
=====  Placement on packages  =====
Package Id.	Core Id.	Processors
0   		0,1,2,3,4,5		(0,6)(1,7)(2,8)(3,9)(4,10)(5,11)
=====  Cache sharing  =====
Cache	Size		Processors
L1	32  KB		(0,6)(1,7)(2,8)(3,9)(4,10)(5,11)
L2	256 KB		(0,6)(1,7)(2,8)(3,9)(4,10)(5,11)
L3	15  MB		(0,1,2,3,4,5,6,7,8,9,10,11)

> head /proc/meminfo 
MemTotal:       32875268 kB
MemFree:        14926632 kB
Buffers:          525708 kB
Cached:         13960396 kB
SwapCached:            0 kB
Active:          9449492 kB
Inactive:        7474852 kB
Active(anon):    2439312 kB
Inactive(anon):   133116 kB
Active(file):    7010180 kB

> cpupower frequency-info
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 1.20 GHz - 2.50 GHz
  available frequency steps: 2.50 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 1.20 GHz and 2.50 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.20 GHz.
  cpufreq stats: 2.50 GHz:2.57%, 2.50 GHz:0.00%, 2.40 GHz:0.14%, 2.30 GHz:0.07%, 2.20 GHz:0.05%, 2.10 GHz:0.06%, 2.00 GHz:0.06%, 1.90 GHz:0.15%, 1.80 GHz:1.44%, 1.70 GHz:1.87%, 1.60 GHz:0.55%, 1.50 GHz:0.26%, 1.40 GHz:0.17%, 1.30 GHz:0.14%, 1.20 GHz:92.48%  (77054)
  boost state support:
    Supported: yes
    Active: yes
    25500 MHz max turbo 4 active cores
    25500 MHz max turbo 3 active cores
    25500 MHz max turbo 2 active cores
    25500 MHz max turbo 1 active cores

I did this and still got overruns with 100 Msps
> cpupower frequency-set -g performance

One thing I noticed was that there's a huge number of interrupts during a test.

> dstat -crimp
----total-cpu-usage---- --io/total- ----interrupts--- ------memory-usage----- ---procs---
usr sys idl wai hiq siq| read  writ|  90    91    92 | used  buff  cach  free|run blk new
  1   1  97   0   0   0|   0     0 |   0     0    49 |3628M  511M 13.1G 14.2G|1.0   0   0
  1   1  98   0   0   0|   0     0 |   0     0    44 |3628M  511M 13.1G 14.2G|  0   0   0
  3   6  91   0   0   0|   0     0 |3503     0   181 |3644M  511M 13.1G 14.2G|1.0   0 1.0 <<<< start benchmark test
  3   8  90   0   0   0|   0     0 |5189     0   265 |3644M  511M 13.1G 14.2G|1.0   0   0
  3   8  89   0   0   0|   0     0 |5032     0   288 |3644M  511M 13.1G 14.2G|1.0   0   0
  3   8  89   0   0   0|   0     0 |5176     0   286 |3644M  511M 13.1G 14.2G|2.0   0   0
  3   8  89   0   0   0|   0  11.0 |5084     0   280 |3644M  511M 13.1G 14.2G|1.0   0   0

Interrupt 90 is niusrpriok in /proc/interrupts.

Could perhaps improve performance through interrupt binding or something like that?

Jared.
------------------------------------------------------
Jared Dulmage
Engineering Specialist
Digital Comm. and Implementation Dept.
Aerospace Corporation
310-336-3140




More information about the USRP-users mailing list