This repository has been archived by the owner on Jun 27, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 129
Injection can not work continually #22
Comments
This likely means that you're injecting data at too high a rate – faster than the NIC is sending the packets. Can you try using the |
Thanks, I have solved the problem. |
Thanks! – can you please say more about what the problem ultimately was and how you solved it? |
@dhalperi |
@Boeing738ng Could you please explain how did you add the scheduling priority to log_to_file. Even I have the same issue on the buffer space availability. Thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If the transmitter send injection packages continually in a rate of 100 packets per second, log_to_file on the receive can only run normally for several minutes, then it would not have any output at all.
I checked usage of the memory, and I found that almost all space of the memory had been buffered.
I want to get CSI informations for several hours.
How to fix it? Is there some parameters I can set to empty buffers automatically?
The text was updated successfully, but these errors were encountered: