Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making sure the USB settings are all set for Linux #10

Open
KamranBinaee opened this issue Apr 14, 2020 · 5 comments
Open

Making sure the USB settings are all set for Linux #10

KamranBinaee opened this issue Apr 14, 2020 · 5 comments

Comments

@KamranBinaee
Copy link
Contributor

KamranBinaee commented Apr 14, 2020

On Linux systems, the USB-FS memory is restricted to 16 MB or less by default.
To increase this limit we should update the grub. More specifically, in /etc/default/grub
Replace:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
with this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.usbfs_memory_mb=160000"

@KamranBinaee KamranBinaee added this to the Release 0.2 milestone Apr 14, 2020
@phausamann phausamann removed this from the Release 0.2 milestone Apr 22, 2020
@phausamann
Copy link
Contributor

160 GB of USB memory seems a bit excessive. Where does this value come from?

@KamranBinaee
Copy link
Contributor Author

That's definitely a typo. The recommended value is anything above 1000 Mb and it's pretty straightforward to calculate. Once we have the final fps and resolution this is what we'd need to do.

@phausamann phausamann reopened this Apr 22, 2020
@phausamann
Copy link
Contributor

Okay, reopening this for now. The link describes an approach that avoids modifying grub settings, I think we should go with that.

@phausamann
Copy link
Contributor

phausamann commented Apr 27, 2020

One image is 2048*1536*3 B = 9 MB, so for 300 buffers we'd need 2700 MB. Not sure how many buffers we need though.

@KamranBinaee
Copy link
Contributor Author

I think that's far more than what we need. Especially because I've set the buffer handling mode to the "latest only" we technically don't use those buffers. Unless for other use cases, where for some reason there's a lag between threads. But even in that case, at least I can't see any condition that we'd need more than that. I also found another repo that uses this parameter to read from three FLIR cameras, which makes sense. We can definitely stress-test this with the higher frame rate Chameleon (half resolution though!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants