Please note what I said. I release interrupts after every byte
READ/WRITTEN, so that the maximal delay to a refresh is the length of
a single byte read/write.
In case it wasn't clear, the only interrupt in use is the ram refresh
interrupt. If it is masked, and triggers, it will execute the handler
when it is unmasked. This means that even a loop on RAM read/write
will not starve RAM of refreshes
[also, why do I keep being told I am submitting too fast, please slow
down. I just posted 2 comments here, that is all. Had to make a new
username :(]
> [also, why do I keep being told I am submitting too fast, please slow down. I just posted 2 comments here, that is all. Had to make a new username :(]
I think there is extra throttling on brand-new accounts, to help keep spam under control. Once your account is a little older it will be less restricted.
Also: welcome, and thanks for joining the discussion!
Comments
Please note what I said. I release interrupts after every byte READ/WRITTEN, so that the maximal delay to a refresh is the length of a single byte read/write. In case it wasn't clear, the only interrupt in use is the ram refresh interrupt. If it is masked, and triggers, it will execute the handler when it is unmasked. This means that even a loop on RAM read/write will not starve RAM of refreshes
[also, why do I keep being told I am submitting too fast, please slow down. I just posted 2 comments here, that is all. Had to make a new username :(]
> [also, why do I keep being told I am submitting too fast, please slow down. I just posted 2 comments here, that is all. Had to make a new username :(]
I think there is extra throttling on brand-new accounts, to help keep spam under control. Once your account is a little older it will be less restricted.
Also: welcome, and thanks for joining the discussion!