On 27/06/2024 15:41, cjohn...@serranosystems.com wrote:
Hi,
Can you help me figure out what the problem is using the modified
example (I provided in last response), a fast machine which has the
tips and tricks implemented?
I directly connected our 64 core / 4 GPU / >250GI RAM workstation with
10G output directly to the X310 10G, which should easily keep up with
200Msps.
I ran the same program I provided above (I just modified your example
program tx_timed_samples.cpp) and now it outputs S’s instead of U’s.
Here is the output:
|cjohnson@demo:~/uhd_versions/uhd_4.4.0.0/host/build/examples$
./tx_timed_samples Creating the usrp device with:
type=x300,addr=192.168.30.2... [INFO] [UHD] linux; GNU C++ version
11.4.0; Boost_107400; UHD_4.4.0.HEAD-0-g5fac246b [INFO] [X300] X300
initialization sequence... [INFO] [X300] Maximum frame size: 8000
bytes. [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev
0.929a [INFO] [X300] Radio 1x clock: 200 MHz Using Device: Single
USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0
RX Dboard: A RX Subdev: UBX RX RX Channel: 1 RX DSP: 1 RX Dboard: B RX
Subdev: UBX RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: UBX TX
TX Channel: 1 TX DSP: 1 TX Dboard: B TX Subdev: UBX TX Setting TX
Rate: 200.000000 Msps... Actual TX Rate: 200.000000 Msps... Setting
device timestamp to 0... [WARNING] [0/Radio#0] Attempting to set tick
rate to 0. Skipping. Send timeout... Send timeout... Send timeout...
Send timeout... Send timeout... Send timeout... Send timeout...
SSSSSSSS (... more S's)|
I verified the interface is setup for 9000 MTU, and that I have made
the adjustments indicated in
https://kb.ettus.com/USRP_Host_Performance_Tuning_Tips_and_Tricks
except for Specture / bios changes). This includes Ring Buffers for
NIC and Network Buffers
|(Below, same for CPU 0-63) analyzing CPU 63: driver: intel_cpufreq
CPUs which run at the same hardware frequency: 63 CPUs which need to
have their frequency coordinated by software: 63 maximum transition
latency: 20.0 us. hardware limits: 800 MHz - 3.50 GHz available
cpufreq governors: conservative, ondemand, userspace, powersave,
performance, schedutil current policy: frequency should be within 800
MHz and 3.50 GHz. The governor "performance" may decide which speed to
use within this range. current CPU frequency is 3.50 GHz.|
_______________________________________________
USRP-users mailing list --usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-le...@lists.ettus.com
I'll note that 'S' errors generally indicate that packets are being
dropped somewhere in the network stack after they leave UHD, and before
they get delivered to the radio.
What type of network interface do you have on your 64-core server?
Are we maybe dealing with a PHY-level issue
that is dropping frames?
What OS are you using? Is this within a VM or on "base metal"??
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
