Project

General

Profile

Fosphor » History » Version 51

sylvain, 02/19/2016 10:50 PM

1 1 sylvain
= gr-fosphor
2
3 51 sylvain
GNU Radio block for RTSA-like spectrum visualization using OpenCL and OpenGL acceleration.
4 1 sylvain
5
http://git.osmocom.org/gr-fosphor/
6
7 51 sylvain
The block has been used successfully on Linux, OSX and Windows.
8
9 21 horiz0n
== Building
10
11 40 sylvain
Warning: Mixed prefix install is not supported. You need to install gr-fosphor in the same prefix as your GNU Radio install. If you used build-gnuradio this will be /usr/local and this is what's used in the instructions below. If you use a packaged version of GNU Radio, it's most likely /usr and the best way is then to make a package for gr-fosphor for your distribution.
12 1 sylvain
13 51 sylvain
=== OS specific notes
14
15
- For OSX you probably just want to use the gr-fosphor [https://trac.macports.org/browser/trunk/dports/science/gr-fosphor/Portfile port in macports]
16
- For Windows you can't use the Visual C++ compiler due to some C99 constructs used in the code that it doesn't support. You can use ICC or compile the C part manually using clang. It has been done, so it's possible albeit not trivial.
17
18 21 horiz0n
=== GLFW3
19
20
Install dependencies
21
22
{{{
23 24 horiz0n
sudo apt-get install cmake xorg-dev libglu1-mesa-dev
24
}}}
25
26 21 horiz0n
Build GLFW
27
28
{{{
29
git clone https://github.com/glfw/glfw
30
cd glfw
31
mkdir build
32
cd build
33 1 sylvain
cmake ../ -DBUILD_SHARED_LIBS=true
34 21 horiz0n
make
35 1 sylvain
sudo make install
36
sudo ldconfig
37
}}}
38
39 51 sylvain
=== OpenCL
40 25 horiz0n
41 51 sylvain
To run fosphor, you need an OpenCL implementation. This can be either a GPU implementation (which will often be the faster option), or a CPU implementation. If available, fosphor will also make use of the CL/GL sharing extension allowing to transfer data efficiently between the OpenCL compute kernels and the OpenGL rendering.
42 1 sylvain
43 51 sylvain
All the implementations listed below have been successfully used with fosphor.
44 1 sylvain
45 51 sylvain
==== NVidia OpenCL
46
47
The NVidia implementation is provided by the binary drivers and support CL/GL sharing very well. Unfortunately the 'nouveau' open-source drivers don't provide OpenCL yet.
48
49 25 horiz0n
 * install [http://www.nvidia.com/object/unix.html NVidia drivers]
50
51 1 sylvain
{{{
52
sudo apt-get install nvidia-opencl-dev opencl-headers
53 26 horiz0n
}}}
54 1 sylvain
55 25 horiz0n
56 51 sylvain
==== AMD GPU OpenCL
57
58 1 sylvain
 * install [http://support.amd.com/en-us/download AMD drivers] (13.4, 13.11 beta6, 13.12 and 14.10 drivers are known to work on linux)
59
 * install [http://developer.amd.com/tools-and-sdks/heterogeneous-computing/amd-accelerated-parallel-processing-app-sdk/ AMD APP SDK]
60
61
62 51 sylvain
==== Intel GPU OpenCL
63 1 sylvain
64 51 sylvain
 * fosphor has been confirmed to work with Iris graphics on OSX.
65
 * It also has been used on linux using the [http://www.freedesktop.org/wiki/Software/Beignet/ beignet opencl]
66
  * It doesn't support CL/GL sharing though, even if you're using the Intel GPU for display
67
  * Performance was disappointing on linux though, there seem to be an unidentified bottleneck.
68
69
70
==== Intel CPU OpenCL
71
72
Intel offers a CPU OpenCL implementation. You need a CPU capable of at least SSE 4.2 to be able to use it. This implementation has been confirmed working with fosphor and is the highest performance of all the CPU OpenCL implementation.
73
74
See [https://software.intel.com/en-us/vcsource/tools/opencl-sdk this page]
75
 
76
77
==== AMD CPU OpenCL
78
79
AMD also has a CPU OpenCL implementation see [http://developer.amd.com/tools-and-sdks/opencl-zone/ this page] for details. It's not quite as fast as the Intel one, but it doesn't require SSE 4.2 which allows it to be used on older processors.
80
81
82
==== pocl
83
84
[http://portablecl.org/]
85
86
This is a free-software OpenCL CPU implementation. It's not where as performant as the Intel/AMD ones, but it's opensource and supported on any platform.
87
88
Note that at the time of writing, you need the git version to use fosphor with it due to a very recently fixed memory leak that fosphor triggers.
89
90
91
==== FreeOCL
92
93
[http://code.google.com/p/freeocl/]
94
95
This is another free-software OpenCL CPU implementation that's also been verified to work with fosphor. It uses whatever C++ compiler is installed on the system as the code generation backend.
96
97
Again, at the time of writing, you need the latest SVN version to use fosphor with it due to some recently fixed bugs that fosphor triggers.
98
99
100
=== gr-fosphor
101
102 25 horiz0n
Build gr-fosphor
103
104 21 horiz0n
{{{
105
git clone git://git.osmocom.org/gr-fosphor
106
cd gr-fosphor
107
mkdir build
108 37 sylvain
cd build
109 21 horiz0n
cmake ..
110
make
111
sudo make install
112
sudo ldconfig
113
}}}
114 1 sylvain
115
Build benchmark tool
116 21 horiz0n
117
{{{
118
cd gr-fosphor/lib/fosphor
119
make
120 25 horiz0n
}}}
121
122 21 horiz0n
Fosphor is known to build successfully on Linux, OSX and Windows.
123 46 sylvain
124
==== Known issues
125 1 sylvain
126 47 horiz0n
 * Some version of ubuntu (like 13.10) have screwed up OpenCL dev files setup and it might be required to manually specify a path to the actual OpenCL library during the cmake step ( like {{{-DOPENCL_LIBRARY=/usr/lib/nvidia-304/libOpenCL.so}}} )
127 46 sylvain
 * When running python flowgraphs on machines with AMD graphics (fglrx driver) and UHD enabled in gr-osmosdr you may experience the following error {{{[!] CL Error (-1001, fosphor/cl.c:268): Unable to fetch platform IDs}}}. This is due to TLS sections in both, AMD OpenCL library and UHD library interfering with each other. A workaround is available through preloading the AMD OpenCL library {{{LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libamdocl64.so osmocom_fft -F}}} (path may vary). C++ flowgraphs are not affected.
128 2 sylvain
129
== Screenshots
130 15 sylvain
131
=== Short video examples
132
133
http://www.youtube.com/watch?v=mjD-l3GAghU
134 1 sylvain
135
{{{
136
#!html
137 15 sylvain
<iframe width="960" height="720" src="http://www.youtube.com/embed/mjD-l3GAghU" frameborder="0" allowfullscreen></iframe>
138
}}}
139
140
141
=== osmocom_fft in fosphor mode
142
143 51 sylvain
Those are when enabling the integrated 'fosphor' mode of osmocom_fft through the -F command line option
144
145
[[Image(GrOsmoSDR:fosphor.png)]]
146 2 sylvain
[[Image(GrOsmoSDR:fosphor2.png)]]
147 3 horiz0n
148
== Bandwidth figures
149
150
There's a benchmark program available which allows to estimate the maximal bandwidth that can be processed with a specific GPU.
151
152
To build it:
153
154
{{{
155
cd gr-fosphor/lib/fosphor
156
make
157
}}}
158
159
Then execute it by providing a prerecorded complex float file (a couple of 100MB should be fine) in gnuradio format.
160
161
{{{
162
./main some.cfile
163
}}}
164
165 14 horiz0n
Try to leave the window to its default size if possible and watch out for the Msps numbers printed out to the console.
166
167
Submit your numbers & help us to create a GPU survey. We are especially interested in the top end and mobile graphics figures.
168 3 horiz0n
169 8 sylvain
||'''CPU'''||'''GPU'''||'''Msps'''||
170 31 horiz0n
||?||AMD R290(X)||WANTED||
171 8 sylvain
||?||NVidia Titan||WANTED||
172 42 horiz0n
||i7-4770K 3.5 GHz||NVidia !GeForce GTX 760||~228||
173 1 sylvain
||?||AMD Radeon HD 7970 (Tahiti)||~220||
174 41 horiz0n
||i5-3570K 3.4 GHz||AMD Radeon HD 7870 (Tahiti)||~220||
175 40 sylvain
||i7-3770K 3.4 GHz||Nvidia GTX 660||~202||
176
||i7-3770K 3.4 Ghz||Nvidia GTX 760||~191||
177 39 ttsou
||i7-4770K 3.5 GHz||Nvidia GTX 650 Ti Boost||~188||
178 49 sylvain
||i5-2500 3.3 GHz||NVidia GTX 460 SE||~129||
179 28 horiz0n
||i5-3570K 3.4GHz||AMD Radeon HD 7870 (Pitcairn)||~112||
180 29 horiz0n
||i5-2500 3.3GHz||NVidia GTX 550 Ti||~110||
181 28 horiz0n
||i5-2500k 3.8GHz||AMD Radeon HD 6850||~100||
182 1 sylvain
||?||NVidia GTX 550 Ti||~97||
183 28 horiz0n
||QC Xeon 2 GHz||Nvidia !GeForce 560 Ti||~73||
184 42 horiz0n
||C2D 2.66 GHz||NVidia !GeForce GT 640 (GK107)||~67||
185 44 sylvain
||i5 2.4 GHz||Intel Iris Pro 5100||~65||
186 48 sylvain
||i7-3610QM||NVidia !GeForce GT 640M LE||~63||
187 42 horiz0n
||i7-950 3.06 GHz||NVidia GT9800||~61||
188
||i5-2500K 4.2 GHz||AMD Radeon HD 6570||~58||
189 30 horiz0n
||C2D 3.00GHz||NVidia !GeForce 9800 GT||~47||
190 43 sylvain
||i5-2520M 2.5 GHz||NVidia GF119M||~46||
191 28 horiz0n
||C2D 2.4GHz||NVidia 9600M GT||~31||
192
||?||NVidia GT330M||~22||
193
||?||NVidia 8600GT||~15||
194
||C2D 2.2GHz||NVidia NVS 140M||~14||
195 1 sylvain
||AMD E350 Fusion APU||AMD Radeon 6310||~12||
196 37 sylvain
||C2Q Q9650 3.00GHz||!GeForce 9300 GE||~11||
197 28 horiz0n
||Atom 330||NVidia ION||~10||
Add picture from clipboard (Maximum size: 48.8 MB)