Skip to content
This repository has been archived by the owner on Jun 27, 2020. It is now read-only.

Injection can not work continually #22

Closed
Boeing738ng opened this issue Mar 31, 2015 · 5 comments
Closed

Injection can not work continually #22

Boeing738ng opened this issue Mar 31, 2015 · 5 comments

Comments

@Boeing738ng
Copy link

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?

@dhalperi
Copy link
Owner

dhalperi commented Apr 1, 2015

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 delay parameter – e.g., send only a single packet per second – and see how long the connection lasts?

@Boeing738ng
Copy link
Author

Thanks, I have solved the problem.

@dhalperi
Copy link
Owner

dhalperi commented Apr 2, 2015

Thanks! – can you please say more about what the problem ultimately was and how you solved it?

@Boeing738ng
Copy link
Author

@dhalperi
I just increased the scheduling priority of the process log_to_file, and now it can run continually without interruption.

@koushikam
Copy link

koushikam commented Feb 23, 2018

@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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants