You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The suggestion is to change these to uint32_t to allow for >64kB ringbuffers. This would only be useful in ports with more than 64kB of heap available, so it may be worthwhile having different versions for different ports.
Or maybe the extra 6 bytes is acceptable across all ports for the sake of simplicity/consistency?
I note that other structures (like bytearray) don't have a 64kB limit, so this would seem to be some sort of precedent for changing the limit.
Code Size
This change would add 6 bytes to RAM usage whenever RingIO is invoked
Implementation
I hope the MicroPython maintainers or community will implement this feature
Code of Conduct
Yes, I agree
The text was updated successfully, but these errors were encountered:
Description
Discussion: #9458 (comment)
Currently RingIO is limited to creating ring buffers of 64kB by the use of the following
uint16_t
variables inringbuf.h
:The suggestion is to change these to
uint32_t
to allow for >64kB ringbuffers. This would only be useful in ports with more than 64kB of heap available, so it may be worthwhile having different versions for different ports.Or maybe the extra 6 bytes is acceptable across all ports for the sake of simplicity/consistency?
I note that other structures (like bytearray) don't have a 64kB limit, so this would seem to be some sort of precedent for changing the limit.
Code Size
This change would add 6 bytes to RAM usage whenever RingIO is invoked
Implementation
I hope the MicroPython maintainers or community will implement this feature
Code of Conduct
Yes, I agree
The text was updated successfully, but these errors were encountered: